reduce mnesia using disk while CB is idle
I've had a few developers complaining that CB uses an inordinate amount of CPU and diskIO on their local development virtual machines. Specifically, while a CB instance is up and there is no traffic, we see the
/opt/couchbase/lib/erlang/erts-5.8.5/bin/beam.smp<code> process hanging out as the first item in <code>top at around 15-25% %CPU. We also find that this process is constantly updating the
/opt/couchbase/var/lib/couchbase/mnesia at about 100k/s (using iostat).
Is there anyway we can reduce the overhead here?
Can we safely move
/opt/couchbase/var/lib/couchbase/mnesia to a ramdisk? What happens if upon restart if we do that? Losing the stats on a dev machine would be fine, but will CB remake the files it needs there are choke if the directory is empty upon a restart?