Tuesday, March 28, 2017
Search
  
Submit your own News for
inclusion in our Site.
Click here...
Breaking News
LG Suses BLU Products Over LTE Patents
Intel Optane Memory Launches Next Month To Boost Your PC
Facebook's Messenger App Will Expose Your Location For An Hour
Samsung To Sell Refurbished Galaxy Note 7s
Transcend Announces Its First PCIe NVMe M.2 Solid State Drive
HTC Says New Companies Join The Vive X Accelerator Program
New HyperX Expands FURY DDR4 Memory Lineup Supports Plug and Play Automatic Overclocking up to 2666MHz
TSMC To Start Producing A11 InFo Chips For New iPhone In April
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
The European Commission Ask Social Media Companies To Comply With EU Consumer Rules
Twitter To Use Algorithms to Tackle Abusive Content
Twitter Pace of Growth Slows
Twitter To Filter Abusive Tweets
Twitter Unveils 360-degree Live Video
Live Video Now Available On Twitter
Facebook, Twitter And Google Are Partnering To Help Curb Spread of Online Terrorist Content
Twitter Android TV App Allows Users To Stream Videos
Twitter Launches Tools To Addressing Online Abuse
Twitter Announces Restructuring and Headcount Reduction, Shuts Down Vine
Twitter To Cut About 8 Percent Of Workforce
Salesforce Will Not Bid for Twitter

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