On Fri, 2010-04-09 at 11:28 -0500, Jonathan Ellis wrote:
> The jit on debian may take longer to warm up by default.
Also, the Debian package will pull in OpenJDK by default, but there is
nothing to stop you from using the Sun JVM (which I assume is what's in
use on the other machines). It is even
Will do, thanks for the advice. :)
On Apr 9, 2010 12:28 PM, "Jonathan Ellis" wrote:
The jit on debian may take longer to warm up by default.
Do 100k ops first before benchmarking.
Benchmark with multiple threads.
And use a known benchmark first like py_stress.
On Fri, Apr 9, 2010 at 11:23 A
The jit on debian may take longer to warm up by default.
Do 100k ops first before benchmarking.
Benchmark with multiple threads.
And use a known benchmark first like py_stress.
On Fri, Apr 9, 2010 at 11:23 AM, Heath Oderman wrote:
> What's interesting for my case is that I put a timer around t
user@cassandra.apache.org
Subject: Re: RE: Very new user needs some troubleshooting pointers
What's interesting for my case is that I put a timer around the thrift method
to insert_batch
Every iteration of that call against debian (any hardware, same network or in
amazon cloud with windows machine
What's interesting for my case is that I put a timer around the thrift
method to insert_batch
Every iteration of that call against debian (any hardware, same network or
in amazon cloud with windows machine in ec2 as well) takes 400,000 ticks.
Super consistent. One thread.
My friends setup with c
