Sunday, March 29, 2015
Search
  
Submit your own News for
inclusion in our Site.
Click here...
Breaking News
Microsoft Lists Windows 10-Compatible Phones
Intel in Talks to buy Altera: report
MediaTek Releases New High-end Smartphone Helio SoC
Google To Get Into The Operating Room
Data Requests To Microsoft Decreased
Google Defeated in English Court - Decision Opens Door for Litigation by Millions of British Apple Users
LG G4 Smartphone Coming Late April
BlackBerry Posts Quarterly Profit
Active Discussions
how to copy and move data files to dvd-rw
cdrw trouble
Need serious help!!!!
burning
nvidia 6200 review
Hello
Burning Multimedia in track 0
I'm lazy. Please help.
 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
Twitter Launches Periscope Live Video Streaming App
IBM Delivers Cloud Data Services with Twitter Built-In
Twitter To Offer More User Safety Features
Content Removal Requests To Twitter Increased
Twitter Reports Strong Revenue But User Growth Slows
Tweers may Be Returning to Google Search
Twitter To Offer Ads To Outside Websites
Twitter Gets Group Messaging and Video Recording
Twitter To Show You Tweets That You Have Missed
Twitter Buys Indian Start-up ZipDial
Twitter Lets You Easier Flag Abusive Tweets
Twitter Tracks Apps Installed On Your Device, Introduces Offers

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