CPU usage

I’ve noticed that EventStore by default consumes quite a CPU. In my case this is ~13% without touching it (with fresh start). Anyone else experienced same? The reason I want to lower CPU usage is that I run other services like elasticsearch, mysql, … on my development environment and I’m just curious what it is doing and how I can lower CPU usage.

So here is how I’ve run it for test (note that I’ve deleted /mnt/eventstore-tmp before running run-node.sh)

./run-node.sh --db /mnt/eventstore-tmp/db --log /mnt/eventstore-tmp/logs --stats-period-sec 120 --run-projections NONE

EventStore info

▒ eventstore ./run-node.sh --version

EventStore version (release-v3.0.5/a9a82d955a0ac1db548b1873fa3be66923dc6032, Tue, 26 May 2015 18:51:16 +0000)

Ubuntu info:

▒ eventstore lsb_release -a

No LSB modules are available.

Distributor ID: Ubuntu

Description: Ubuntu 12.04 LTS

Release: 12.04

Codename: precise

If any more info needed, please let me know.

I think if you profile you will find:
is causing the usage (internal timings). I will try something smarter

@Greg Young,

Did you find anything, we are pr 3.9.2 still experiencing the issues described by Aleš Blaznik

I’m also having problems with this, is there a github issue for this that I can follow so I know when a fix has been issued?

I am seeing the same.

Newly installed eventstore, running all default projections. uses about 6% CPU (probably 6% of one cpu core, but spread out amongst multiple cores) according to top.
Looking at the dashboard, it seems it is running up ~170 items/s continuously:

MainQueue ~10
ProjectionsMaster ~20
Storage Chaser ~100
Timer ~30
Workers ~10


I created a GitHub issue for it: https://github.com/EventStore/EventStore/issues/1212

This is not an issue an it is actually doing work. You will also see
statistics running amongst other things.

Sure it might be doing stuff but 25% CPU usage for an idle database that I haven’t inserted anything in is way to much

Someone else just quoted 6% of one core.

That said try pulling a flame graph to see what is using CPU in your
higher case.