couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From René Rössler (JIRA) <j...@apache.org>
Subject [jira] [Created] (COUCHDB-1895) Heartbeat does not always start after connection is established
Date Wed, 25 Sep 2013 13:32:03 GMT
René Rössler created COUCHDB-1895:
-------------------------------------

             Summary: Heartbeat does not always start after connection is established
                 Key: COUCHDB-1895
                 URL: https://issues.apache.org/jira/browse/COUCHDB-1895
             Project: CouchDB
          Issue Type: Bug
          Components: HTTP Interface
            Reporter: René Rössler


I have a database with ~5000 documents and a update sequence of ~100,000.
If I start a filtered, continuous changes stream with heartbeat set to 1000, I get the first
heartbeat after ~1 seconds.
If I start the same changes stream with a heartbeat of 10,000, I get the first heartbeat after
~10 seconds.
But if I start the same changes stream with a heartbeat of 10,000, I get the first heartbeat
after ~57 seconds and the second heartbeat ~2 seconds later.
Getting all the changes without a continuous feed takes about 15 seconds.

I measured the timings with this command:

bq. date && wget --quiet "http://localhost:5984/database/_changes?filter=design/filter&feed=continuous&heartbeat=30000&since=0"
-O /dev/stdout |perl timing.pl

{code:title=timing.pl|borderStyle=solid}
#!/usr/bin/perl

use POSIX qw(strftime);

while(!eof(STDIN))
{
        $line=<STDIN>;
        print strftime("%F %T", localtime), $line;
}
{code}

Couchdb is version 1.4.0 installed via homebrew on is Mac OS 10.8.5.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message