We've seen big performace degradation when we tested 1024 topics, so we've
opted to go for a much smaller topic count (< 100).

On the read side, I think performance is largely driven by the ability of
the operating system to effectively cache access to #partitions*topic
files. Clearly if you divide your available memory by 1024 topics you'll
have less in the file cache per topic than you would with only 3 topics
(for example).
On Wed, Mar 27, 2013 at 11:14 AM, Jun Rao <[EMAIL PROTECTED]> wrote:
Matthew Rathbone
Foursquare | Software Engineer | Server Engineering Team
[EMAIL PROTECTED] | @rathboma <http://twitter.com/rathboma> |

NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB