couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Damien Katz <dam...@apache.org>
Subject Re: View Building Grinds System to Halt
Date Thu, 05 Aug 2010 18:36:36 GMT
Can you post your design doc with the views in it? Keep in mind, CouchDB builds all views in
a design doc at the same time, so it might not be the view you are accessing that's using
up resources, but another included in the same design doc.

-Damien


On Aug 5, 2010, at 11:29 AM, Gordon Leland Hempton wrote:

> This also seems to happen whenever I cleanup views: beam.smp uses all the
> systems memory and then disappears, however the log message doesn't show up.
> 
> Views work totally fine on databases that are small in size.
> 
> Anyone have any recommendations?
> 
> On Wed, Aug 4, 2010 at 4:07 PM, Gordon Leland Hempton <ghempton@gmail.com>wrote:
> 
>> After looking at the logs, it looks pretty bad:
>> 
>> [Wed, 04 Aug 2010 22:57:28 GMT] [info] [<0.12883.0>] 127.0.0.1 - - 'GET'
>> /trademark/_design/Trademark/_view/by_filingDate?limit=10&stale=ok&descending=true&include_docs=true
>> 200
>> 
>> [Wed, 04 Aug 2010 22:57:52 GMT] [error] [emulator] Error in process
>> <0.12957.0> with exit value: {badarg,[{erlang,binary_to_term,[<<1885695232
>> bytes>>]},{couch_file,pread_term,2},{couch_db,make_doc,5},{couch_db,open_doc_int,3},{couch_view_updater,load_doc,5},{couch_view_updater,'-update/2-fun-2-',8},{couch_btree,stream_kv_node2,8...
>> 
>> Anyone know where to start?
>> 
>> I am running Ubuntu 10.04 server with couchdb 1.0 installed from source. I
>> have made sure the xulrunner settings are correct.
>> 
>> Thanks,
>> 
>> On Wed, Aug 4, 2010 at 12:18 PM, Gordon Leland Hempton <ghempton@gmail.com
>>> wrote:
>> 
>>> I am working with a database of ~10 mil docs and 30GB size. I am trying to
>>> build a view consisting of a single field as the key and a null document.
>>> 
>>> After creating the view and trying to access it, the couchdb beam.smp
>>> command eventually goes up to 12.3GB virtual memory and uses 3.7GB of
>>> physical memory. Memory is clearly the bottleneck as the CPU usage is around
>>> 5-15%. My system only has 4GB of memory so naturally all this paging is
>>> slowing everything down to a crawl.
>>> 
>>> After a few minutes this usage will go back down, but it will get to the
>>> same levels every time I access the view (which is still building and has
>>> been for 12 hours).
>>> 
>>> Is this normal? How can I improve this?
>>> 
>>> --
>>> Gordon L. Hempton
>>> http://componentlab.com
>>> http://hempton.com
>>> 
>> 
>> 
>> 
>> --
>> Gordon L. Hempton
>> http://componentlab.com
>> http://hempton.com
>> 
> 
> 
> 
> -- 
> Gordon L. Hempton
> http://componentlab.com
> http://hempton.com


Mime
View raw message