Monday, April 23, 2018
Search
  
Submit your own News for
inclusion in our Site.
Click here...
Breaking News
Samsung Launches Six Original Series on Samsung VR Video Service on Gear VR
Facebook Says Users Are Not Products, the Social Network Is
European Regulators Investigate Apple's Proposed Acquisition of Shazam
Amazon is Working on Home Robots: report
7nm Volume Production to Fuel TSMC's Profits This Year
Toshiba Weighs Memory Chip Unit Options
Google Chat Launches to compete with Apple's iMessage
ASUS ZenFone Max Pro M1 Brings Great Value Priced at Just $165
Active Discussions
Which of these DVD media are the best, most durable?
How to back up a PS2 DL game
Copy a protected DVD?
roxio issues with xp pro
Help make DVDInfoPro better with dvdinfomantis!!!
menu making
Optiarc AD-7260S review
cdrw trouble
 Home > News > General Computing > Twitter...
Last 7 Days News : SU MO TU WE TH FR SA All News

Friday, October 08, 2010
Twitter's New Search Architecture


Twitter launched a new backend for search on twitter.com during the last few weeks.

Twitter?s real-time search engine was, until very recently, based on the technology that Summize originally developed. However, scaling the old MySQL-based system had become increasingly challenging. About 6 months ago, Twitter decided to develop a new search architecture that is based on a highly efficient inverted index instead of a relational database. Twitter chose Lucene, a search engine library written in Java, as a starting point.

Twitter's demands on the new system are immense: With over 1,000 TPS (Tweets/sec) and 12,000 QPS (queries/sec) = over 1 billion queries per day (!) Twitter already put a very high load on our machines. In addition to these scalability requirements, Twitter also need to support extremely low indexing latencies (the time it takes between when a Tweet is tweeted and when it becomes searchable) of less than 10 seconds. Since the indexer is only one part of the pipeline a Tweet has to make it through, Twitter needed the indexer itself to have a sub-second latency.

However, Lucene has several shortcomings for real-time search. That?s why Twitter rewrote big parts of the core in-memory data structures, especially the posting lists, while still supporting Lucene?s standard APIs. This allows Twitter to use Lucene?s search layer almost unmodified. Some of the highlights of the changes include:

* significantly improved garbage collection performance
* lock-free data structures and algorithms
* posting lists, that are traversable in reverse order
* efficient early query termination

Twitter estimates that it is only using about 5% of the available backend resources. Twitter's new indexer could also index roughly 50 times more Tweets per second than Twitter currently gets.

The first difference users might notice is the bigger index, which is now twice as long -- without making searches any slower. And, maybe most importantly, the new system is versatile and extensible, which will allow Twitter to build new features faster and better.


Previous
Next
Firefox 4 Beta for Android and Maemo is Now Available        All News        Opera To Participate In in Open Screen Project
Google Testing Self-driving Cars     General Computing News      Opera To Participate In in Open Screen Project

Get RSS feed Easy Print E-Mail this Message

Related News
Social Networks Have One Hour to Remove Online Terrorist Content, Europe Says
Twitter Makes it Easier to Save and Share Tweets
Social Media Need to Do More to Comply With EU consumer Rules
Twitter Posts Profit, But User Base Growth is Still Slow
Twitter Developing video Sharing Tool
New Twitter Rules Aim Hateful Conduct and Abusive Behavior
Twitter Makes It Easier For Users to Create Threads
Twitter Now Allows you to Tweet 280 Characters
Twitter Employee Deactivated Trump's Account
Twitter Reports Profit For the First Time As Sales and User Grow
Twitter to Show Who Pays for Ads
Twitter's Disclosures About Russia-linked Accounts are not Enough, U.S. senator Says

Most Popular News
 
Home | News | All News | Reviews | Articles | Guides | Download | Expert Area | Forum | Site Info
Site best viewed at 1024x768+ - CDRINFO.COM 1998-2018 - All rights reserved -
Privacy policy - Contact Us .