On Wed, Jan 13, 2010 at 3:02 PM, Roger Binns <[email protected]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > [I wrote a personal query to Damien which he asked me to repeat here.] > > Both 620 and 623 were closed by Damien because they lacked objective > criteria. For both tickets there are criteria I consider objective :-) > There are also suggestions on how to address the issues. > > Consequently my query is if the criteria are not objective enough, does > Damien not agree with them, not care about the underlying issues, think that > a 10 million document/2GB raw json data set is outside the scope of what > CouchDB should cope with, want this stuff in the wiki etc?
I think the first step is to write measurements. Good job, you've done this. The ticketing system should be for smaller scope issues, I think. Optimizing the view server is an agreed goal of the community. Probably the best way to help is to take a look at all the work Damien's done in trunk (the pipelining) and perhaps the parallel writers optimization he has. We could really use a way to take the benchmarks you ran, and put them into the buildbot. If you think the high-consistency design can never meet your needs, you should work on alternate indexers. However, there are a lot of low-hanging fruit around - I think we can be fast enough. The key is to approach them constructively, and realize that there's already a lot of working going on along these lines. The best time to create tickets for larger issues, is when you have code. For small bugs, it's good to create a ticket so we don't forget. I'd love to see something like your benchmark harness moved into the build process. Chris > > Roger > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAktOUP4ACgkQmOOfHg372QS/hQCfSP9Edy+wrZRFwItFmDD3mNcN > yyIAn2z9XvJigm2xKk/r4CgAUqZp1t/i > =JMLG > -----END PGP SIGNATURE----- > > -- Chris Anderson http://jchrisa.net http://couch.io
