Without thinking too hard, could this be an effect of fsync in a VM? If you're feeling experimentally inclined, you could try and see the performance after commenting out the two calls to fsync in write header to see what happens.
Also, the idea that fsync is slow in a VM could be outdated. Its just one of those fuzzy memories of reading something somewhere as opposed to any personal experience. HTH, Paul Davis On Thu, Jan 29, 2009 at 3:40 PM, Niket Patel <[email protected]> wrote: > While views are generating first time on 6000 docs size db. ( same database > for both machines ) > Mac ( 2Ghz core 2 duo, 2 GB ) take few seconds > Ubuntu Linux ( 2.4 Ghz 1.7 GB ) on Amazon takes forever ( 60 mins still > waiting ) > > CouchDB version : 0.9.0a738990-incubating > Erlang Version : > - Mac : Erlang (BEAM) emulator version 5.6.5 [source] [smp:2] > [async-threads:0] [kernel-poll:false] > - Linux : Erlang (BEAM) emulator version 5.6.5 [source] [async-threads:0] > [hipe] [kernel-poll:false] > > One observation, First "couchjs" and "beam" processes are running when view > generation starts after few second couchjs goes away but 'beam' ( > /usr/local/lib/erlang/erts-5.6.5/bin/beam ) keep running consuming 45% CPU > all time >
