Hi Kishore,

Since a message is only exposed to the consumers after it is flushed. Maybe
you can try lower log.default.flush.interval.ms which controls the maximum
time that a message in any topic is kept in memory before flushed to disk (
by default it's 3000ms )

ref - http://kafka.apache.org/07/configuration.html

Best Regards,
Stone


On Fri, May 17, 2013 at 12:46 PM, Kishore Kopalle <kkopa...@gmail.com>wrote:

> Hello All,
>
> I am evaluating Kafka for use in a real time financial product. I am tying
> to calculate the time it takes for a message to be fetched by the consumer
> after it has been sent by a producer. I am finding that this takes a long
> time of between 900-1200 ms per message on Windows 7 single core processor.
> Is this the expected result? This seems to be very slow. All my configs are
> default except for the following properties being put:
>    props.put("zk.sessiontimeout.ms", "400");
>     props.put("zk.synctime.ms", "200");
>     props.put("autocommit.interval.ms", "1000");
>
> Am I missing any configuration steps for server/producer/consumer?
>
> Thanks in advance for answering,
> Kishore
>

Reply via email to