Hi,
sorry, I saw the couchdb user, mistaking it for a process. Actually what
takes most of the cpu is beam.smp.
Yes, I do have some reduce functions, 90% of them are simply _count.
On the Futon status screen I see only replication jobs, which are 100%
completed.
There is nothing special in the couch.log, either.
Database sizes are very small, few Mb.
Now, it's midnight here, there is no activity whatsoever in the
application and beam.smp swings between 3 and 15% cpu.
For the last 10 hours it has 8+ hours TIME in 'top'.
Host is latest Ubuntu, Couch version is 1.6.1.
On 07-Jul-15 10:08 PM, Adam Kocoloski wrote:
Hi Kiril, no it’s not normal. Did you mean `couchjs` when you said `couchdb`?
If so it’s likely related to indexing. Do your views have custom reduce
functions? A poorly-behaved custom reduce function (e.g. one that doesn’t
really “reduce” its output) could yield very slow indexing. Does the dashboard
indicate any indexing jobs ongoing?
Adam
On Jul 7, 2015, at 1:42 PM, Kiril Stankov <[email protected]> wrote:
Hi,
I've loaded 15K docs to a single DB, with 7 views, which do not emit docs (just
id's).
Since then (4 hours now) the CPU is constantly high (~15-20%) with most of it
divided between couchdb and beam.smp.
In addition couch became significantly slower than before (when there were ~ 3K
docs).
Is that normal? Can it be related to indexing? How long can it take?
Thanks in advance.
Kiril.
