Beam and couchjs pipe data back and forth during view generation. While the one works, the other waits. The scheduler is smart enough to keep the processes local to a single CPU. Otherwise it's be even more expensive. Cheers Jan -- On 04.05.2009, at 12:50, Elf wrote: > Hello. > I'm using couchdb-0.9 (erlang 13.2) on my linux server with 4 CPUs > (Core 2 Quad). > Every time couchdb needs to reindex views, i see 2 serious processes > in htop - beam and couchjs. Each of them eats < 100% of 1 cpu, and sum > of their usage is about (but not greater) 100% of 1 cpu (80/20, 70/30 > and so on). > Can somebody explain, why that 2 different processes (they have > differend PIDs) doesn't used different cpus - (one process for cpu)? > > > -- > ---------------- > Best regards > Elf > mailto:elf2001@gmail.com >