more info g...@goto-laptop:~/Downloads$ time curl http://localhost:5984/testdb/02431575b260bcf27a0733c6810010a7 > /dev/null % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 9148k 100 9148k 0 0 1325k 0 0:00:06 0:00:06 --:--:-- 1867k
real 0m6.914s user 0m0.010s sys 0m0.020s g...@goto-laptop:~/Downloads$ On Fri, Aug 27, 2010 at 12:20 AM, sgoto <[email protected]> wrote: > couchdb is taking a lot of time to return me (somewhat) large json > documents. it is taking me 8 seconds to return me a 4MB doc (json doc, not > attachments) from localhost (which should remove some of the > network/bandwidth latency), which doesn't sound right. > > real 0m8.606s > user 0m0.010s > sys 0m0.100s > g...@goto-laptop:~/Downloads$ time curl > http://localhost:5984/testdb/02431575b260bcf27a0733c6810010a7 > > am i missing something ? ideas ? > > On Wed, Aug 25, 2010 at 4:49 PM, sgoto <saork [email protected]> wrote: > >> >> >> On Wed, Aug 25, 2010 at 4:34 PM, J Chris Anderson <[email protected]>wrote: >> >>> >>> On Aug 25, 2010, at 4:22 PM, sgoto wrote: >>> >>> > hey everyone, >>> > >>> > i need to store some large blobs in the doc json (base64 encoded), >>> is >>> > there any documentation on how large the json doc can be ? >>> > >>> >>> >> configurable at 4GB by default >>> >>> >> are there precedents of users of couchdb storing documents that large ? is >> there any work around for validating attachments (i heard we are adding >> sha1/md5 hashes but i'm not sure if that is ready yet) ? any alternatives ? >> >> >>> > long story: attachments are not sent to function validators, which >>> > means i can't controls whether it is ok or not to have them there or >>> not >>> > (except for user auth, which doesn't work with replication). >>> > >>> > thanks, sam >>> > >>> > -- >>> > f u cn rd ths u cn b a gd prgmr ! >>> >>> >> >> >> -- >> f u cn rd ths u cn b a gd prgmr ! >> > > > > -- > f u cn rd ths u cn b a gd prgmr ! > -- f u cn rd ths u cn b a gd prgmr !
