Sean,
I will try tweaking those settings you suggest.
In terms of the CPU usage we see 60% on average across the whole 12
CPU's so approx 720-790% in total with no one cpu maxed out.
Dave
On 9 Dec 2010, at 14:04, Sean Cribbs wrote:
> If you're using ETS, then yes that makes
If you're using ETS, then yes that makes sense that the majority of the time
would be CPU (there's no disk to wait on!). One thing - when you say 60% of
available CPU, is that 60% of one core, or 60% of 12 cores (sometimes reported
as 720%)? The latter seems highly unlikely.
There are some gen
Sean,
We have used the ETS backend, to rule out Disk IO as much as possible
and we are pretty sure that our memory IO is fine, this leaves either Network
IO being a factor or the erlang VM itself ( highly unlikely ). In further
testing we also discovered that just using 1 node in the ri
David,
It's expected that, especially when running basho_bench, your cluster will not
use that much CPU. Riak is mostly I/O-bound, which is a good thing (vs. wasting
CPU not delivering data to you). I would definitely expect network and disk
(and possibly RAM) to be the primary limiting factor
We are currently running a ring of 3 machines each machine with 12 cores, and
have noticed that we seem to only be using 60% of available CPU ( other 40% is
spent idle ) when running basho bench against the cluster. We have tried
changing the 'n_val' from 3 to 1 and also the backend from bitcask
