We are hitting a few walls with a CouchDB deployment and both Damien and I are a bit puzzled. This posting tries to attract someone with a clue to help us out. Our problems might result from not understanding the documentation correctly, but with evidently inaccurate material, we stand little chance. Here it goes.
Spidermonkey hogs memory
Or its garbage collection is a little ineffective. CouchDB uses Spidermonkey, Mozilla’s Javascript engine to create views on its databases. The user provides a Javascript function and CouchDB uses Spidermonkey to determine which documents to include in a View. The Javascript script that evaluates and executes the user’s function runs as a daemon.
We have a global variable there, map_results
(declaration in line 19) that gets reset to {}
for
each document and map …