5å¹´ã«ä¸åº¦ãå½ãè¡ãå½å¢èª¿æ»ãã¯ãã¾ã£ã¦ãã¾ãã ãã®å½å¢èª¿æ»ã®å é¨ä½æ¥ãè¡ãæ¥è ãæ¯æ´ããããã®ã·ã¹ãã ããã»ã¼ã«ã¹ãã©ã¼ã¹ã»ãããã³ã ã®ã¯ã©ã¦ãã«ãã£ã¦æ§ç¯ããã¦ãããã¨ãåç¤¾ç¤¾é· å®éæ 次æ°ã®ãã¤ã¼ãã§æããã«ãªãã¾ããã ã¯ããä»°ãéãã§ãããã¼ããã¼æ§çµç±ã§ããã使ã£ããã次ã¯5å¹´å¾ã§ãããããã¯ã¢ãããç½å®³å¯¾çãç¡æã§ãéçºæéãæ°é±éã§ããRT @tera3pokole: @udaeiji ä»åã®å½å¢èª¿æ»ã®ã·ã¹ãã ã御社ãè«ãè² ãããã®ã§ãããããless than a minute ago via Echofonå®éæ 次 udaeiji ãã®è¨äºã§ã¯å½åãã»ã¼ã«ã¹ãã©ã¼ã¹ã»ãããã³ã ã®ã·ã¹ãã ãæ±äº¬é½ãã¢ãã«å°åã¨ãã¦è¡ãããå½å¢èª¿æ»ã®ãªã³ã©ã¤ã³åçã«ä½¿ããããã®ã¨æ¸ãã¾ããããééãã§ããããªã³ã©ã¤ã³åçã®ãã¼ã¿ã¯ã»ã¼ã«ã¹ãã©ã¼ã¹ã»ãããã³ã ã¯ä½¿ããã¦ãããããã¼ã¿ãå½å
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
ãªãªã¼ã¹ãé害æ å ±ãªã©ã®ãµã¼ãã¹ã®ãç¥ãã
ææ°ã®äººæ°ã¨ã³ããªã¼ã®é ä¿¡
j次ã®ããã¯ãã¼ã¯
kåã®ããã¯ãã¼ã¯
lãã¨ã§èªã
eã³ã¡ã³ãä¸è¦§ãéã
oãã¼ã¸ãéã
{{#tags}}- {{label}}
{{/tags}}