writes are also concurrent in a sense, though only one process is writing to the .couch file. If I send a 100 mib attachment and you send one at the same time, then chunks from each of our attachments are written to disk as they are being sent. We both get a 201 at about the same time.
B. On Wed, Mar 24, 2010 at 12:04 PM, Vasili Batareykin <[email protected]> wrote: > i think this is right place) > > 2010/3/24 Robert Newson <[email protected]> > >> There are numerous ways that attachment retrieval performance can be >> improved, I'm just explaining why you're seeing the numbers you >> reported. >> >> Turning off chunking would also be a code change, one that I don't >> expect will make it into the product, since it would degrade >> concurrent writer behavior. >> >> hmhmh as i read docs there is no concurrent writing, only concurent read. > i'm wrong? > > > >> My current favorite proposed enhancement is to support external >> attachments (where the attachment is written to its own, separate >> file). I haven't started work on a patch for this, yet, but it should >> give all the advantages of apache2/sendfile while still allowing >> couchdb replication, etc. >> >> this will be nice. >
