Return-Path: X-Original-To: apmail-kafka-users-archive@www.apache.org Delivered-To: apmail-kafka-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DB784EDA2 for ; Mon, 28 Jan 2013 14:02:57 +0000 (UTC) Received: (qmail 13372 invoked by uid 500); 28 Jan 2013 14:02:57 -0000 Delivered-To: apmail-kafka-users-archive@kafka.apache.org Received: (qmail 12932 invoked by uid 500); 28 Jan 2013 14:02:53 -0000 Mailing-List: contact users-help@kafka.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@kafka.apache.org Delivered-To: mailing list users@kafka.apache.org Received: (qmail 12892 invoked by uid 500); 28 Jan 2013 14:02:51 -0000 Delivered-To: apmail-incubator-kafka-users@incubator.apache.org Received: (qmail 12888 invoked by uid 99); 28 Jan 2013 14:02:51 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Jan 2013 14:02:51 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of danny@myheritage.com designates 207.126.144.139 as permitted sender) Received: from [207.126.144.139] (HELO eu1sys200aog115.obsmtp.com) (207.126.144.139) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 28 Jan 2013 14:02:42 +0000 Received: from mail-ie0-f199.google.com ([209.85.223.199]) (using TLSv1) by eu1sys200aob115.postini.com ([207.126.147.11]) with SMTP ID DSNKUQaE7WI9rWL4RZT836mPQuTWpH2nv7/0@postini.com; Mon, 28 Jan 2013 14:02:22 UTC Received: by mail-ie0-f199.google.com with SMTP id c13so1293693ieb.6 for ; Mon, 28 Jan 2013 06:02:20 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:x-received:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=/e4e/oCfEvaNzfu/UAdOu3UDzv/c3QUIxKEKpO33MGw=; b=aes5+1Nc41aH9IUz1Ra3bwDIJ/3wWS1/Dzwy6pyFSq0yUUeGL+5tpv8tlcGj+ur1qA UpOl0gtMOLvFPX5R/HsHdMubkKiizGPcKpIDyhkYoM4u8JZjA/8UDhoY4m2Z8Sezce1A JRK/rX3S/vh62QIV2C6s2FtI/AyFJjFXTAr1nK4Jjc0AOWcxTfwL85U0NNQTSHiqWnvd lYbUJuAQutDMF7FfLkV1yiKR4Bu8IVIUBIb11OrKUmEfZjkCZq7veeZM2fYg9J26kZ45 9Wua3uABsVfEV89XevU6TMq57OrTCtXxBZ/NAnuSoM4NI2d59tgD8S1aGDJdVQ0Kxdr9 OzBA== X-Received: by 10.50.34.193 with SMTP id b1mr5113392igj.89.1359381740699; Mon, 28 Jan 2013 06:02:20 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.50.34.193 with SMTP id b1mr5113384igj.89.1359381740607; Mon, 28 Jan 2013 06:02:20 -0800 (PST) Received: by 10.42.46.1 with HTTP; Mon, 28 Jan 2013 06:02:20 -0800 (PST) Date: Mon, 28 Jan 2013 16:02:20 +0200 Message-ID: Subject: Response time degradation From: Danny Yeshurun To: kafka-users@incubator.apache.org Content-Type: multipart/alternative; boundary=14dae9340fafc357a804d459b955 X-Gm-Message-State: ALoCoQkml63M5cn542yE+IX7lRylHGmJS/Nkp3QJO/wOyhjjGZWhq71HzEFolG/+YwARQfI3B5qKJjPAuv+24yk8uyGJLQqOUYCxxeFrJWeACcqtw+towCDDQQ913yMKgvlphAy+INevsuSUyT2OFm0DqeTV/H89jV7XisZP/LTvSJzKiQceweiDULY0JAtXKkbToW3Cn4p9 X-Virus-Checked: Checked by ClamAV on apache.org --14dae9340fafc357a804d459b955 Content-Type: text/plain; charset=ISO-8859-1 Hi, I am using Kafka 0.7.2 I have a consumer that tries to fetch messages from several partitions on the same broker (and topic). The consumers issues a fetch request per partition, if there are messages to read, it fetches the first one and goes to the next partition to fetch another message and so on (in a loop). When there are not messages in a partition, the consumer will issue another fetch request on the next cycle etc. I noticed that starting with the 2nd fetch request, response time becomes unacceptable, i.e. reading back the response from the broker takes ~0.04 second (while it took ~0.0006 sec on the first time). This behavior is consistent over different runs. Any idea? Thanks, Danny --14dae9340fafc357a804d459b955--