[jira] Commented: (COUCHDB-620) Generating views is extremely slow - makes CouchDB hard to use with non-trivial number of docs

2010-01-10 Thread Dirkjan Ochtman (JIRA)
[ https://issues.apache.org/jira/browse/COUCHDB-620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798602#action_12798602 ] Dirkjan Ochtman commented on COUCHDB-620: - I was recently thinking about this and

[jira] Created: (COUCHDB-620) Generating views is extremely slow - makes CouchDB hard to use with non-trivial number of docs

2010-01-10 Thread Roger Binns (JIRA)
Generating views is extremely slow - makes CouchDB hard to use with non-trivial number of docs -- Key: COUCHDB-620 URL: https://issues.apache.org/jira/browse/COUCHDB-620

Re: Space (in)efficiency

2010-01-10 Thread Roger Binns
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Roger Binns wrote: > I'll do the requisite experiments this weekend trying to see what has the > most effect on file size And the answer is length. It is quicker to add documents with sequential (sorted) _ids. The length of the _id field has an ef

Re: svn commit: r897509 - /couchdb/trunk/etc/couchdb/default.ini.tpl.in

2010-01-10 Thread Chris Anderson
On Sun, Jan 10, 2010 at 4:24 PM, Roger Binns wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Chris Anderson wrote: >> I'm not feeling super-strong about this. However, making the default >> sequential seems like it will preempt a lot of the problems people >> tend to show up asking ab

Re: svn commit: r897509 - /couchdb/trunk/etc/couchdb/default.ini.tpl.in

2010-01-10 Thread Roger Binns
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris Anderson wrote: > I'm not feeling super-strong about this. However, making the default > sequential seems like it will preempt a lot of the problems people > tend to show up asking about. There are several issues conflated together: - - When d

Re: svn commit: r897509 - /couchdb/trunk/etc/couchdb/default.ini.tpl.in

2010-01-10 Thread Chris Anderson
On Sun, Jan 10, 2010 at 8:25 AM, Paul Davis wrote: > Was there a discussion I missed somewhere on making sequential uuid's > the default algorithm? We decided against it when applying the patch > from COUCHDB-465 [1] and I still hesitate to use anything other than > completely random as the defaul

Re: svn commit: r897509 - /couchdb/trunk/etc/couchdb/default.ini.tpl.in

2010-01-10 Thread Paul Davis
Was there a discussion I missed somewhere on making sequential uuid's the default algorithm? We decided against it when applying the patch from COUCHDB-465 [1] and I still hesitate to use anything other than completely random as the default. With the sequential algorithm we're leaking doc creation