Twitterã®ãªã¢ã«ã¿ã¤ã æ¤ç´¢æ©è½ãããªã¼ãã³ã½ã¼ã¹ã®Luceneãã¼ã¹ã«ãªã£ãã¨ãTwitter Engineeringããã°ã¸ã®ã¨ã³ããªãTwitter's New Search Architectureãã§ç´¹ä»ããã¦ãã¾ãã ããã¾ã§Twitterã¯ãªã¢ã«ã¿ã¤ã æ¤ç´¢ã«MySQLãã¼ã¹ã®ç¬èªã·ã¹ãã ãå©ç¨ãã¦ãã¾ããããè¦æ¨¡ã®æ¡å¤§ãé£ãããªã£ã¦ããããã6ã«æåã«æ°ã·ã¹ãã ã®æ§ç¯ã決å®ããªã¼ãã³ã½ã¼ã¹ã®æ¤ç´¢ã¨ã³ã¸ã³ã§ããLuceneãé¸æããã¨ã®ãã¨ã§ãã å¾æ¥ã®50åãé«éã«ï¼ æ¤ç´¢ã¨ã³ã¸ã³ã«å¯¾ããè¦ä»¶ã¯ä»¥ä¸ã®ããã«é常ã«å³ãããã®ã§ããã Our demands on the new system are immense: With over 1,000 TPS (Tweets/sec) and 12,000 QPS (queries/sec) = over 1 billion
{{#tags}}- {{label}}
{{/tags}}