Hi Kevin,
   Thanks for the reply !
I do not know the exact brand of SSD in my office PC. But the SSD is  only 1 
year old,  and it is far from full. 

On both of office PC and home PC, I untared Apache Cassandra 2.1.0 and then 

        run "cassandra -f " with the default config,   then

        run cassandra-stress 

Both PCs  have Oracle Java 1.7.0_40.

I have noticed there are some parameters for SSD in cassandra.yaml, which I 
have adjusted, but with no improvement. 


It  puzzles me Cassandra on  my office PC, with far better hardware,  could be 
100% slower than my home PC. 



Shing







On Saturday, 27 September 2014, 5:12, Kevin Burton <[email protected]> wrote:
 


What SSD was it?  There are a lot of variability in terms of SSD performance.

1.  Is it a new vs old SSD?  Old SSDs can become slower if they’re really worn 
out

2.  was the office SSD near capacity holding other data?

3.  what models were they?

SSD != SSD… there is a massive amount of performance variability out there.

… also … more data is needed.  JDK versions the same?  cassandra versions the 
same?

what about the config?


On Fri, Sep 26, 2014 at 2:39 PM, Shing Hing Man <[email protected]> wrote:

Hi,
>  I have run   cassandra-stress write and  cassandra-stress read  on my office 
> PC and on my home PC. 
>
>
>Office PC : Intel Core i7-4479, 8  virtual core, 16G RAM, 500G SSD Home PC : 
>Intel Xeon E3-1230V3, 8 virtual core,  8G RAM, 500G SATA disk.
>
>
>From the cassandra-stress result (please see below), it seems  Cassandra is 
>more than 100% performant on my home PC than the office PC.   I am expecting 
>the other way around, as my office PC has much  better hardware. 
>
>
>
>Office : Intel Core i7-4479, 9  virtual cores, 16G RAM, 500G 
>SSDcauchy:~/installed/cassandra/tools/bin> ./cassandra-stress write 
>Running with 8 threadCount
>Results:
>op rate                   : 11264
>partition rate            : 11264
>row rate                  : 11264
>latency mean              : 0.7
>latency median            : 0.4
>latency 95th percentile   : 0.9
>latency 99th percentile   : 1.6
>latency 99.9th percentile : 5.3
>latency max               : 325.3
>Total operation time      : 00:02:40
>
>
>
>
>cauchy:~/installed/cassandra/tools/bin> ./cassandra-stress read 
>Running with 8 threadCount
>Results:
>op rate                   : 13702
>partition rate            : 13702
>row rate                  : 13702
>latency mean              : 0.5
>latency median            : 0.5
>latency 95th percentile   : 0.8
>latency 99th percentile   : 1.4
>latency 99.9th percentile : 3.4
>latency max               : 67.1
>Total operation time      : 00:00:30
>
>
>---------------------------------------------------
>--------------------------------------------------
>
>Home : Intel Xeon E3-1230V3, 8 virtual core,  8G RAM, 500G SATA disk.
>
>
>matmsh@gauss:~/installed/cassandra/tools/bin> ./cassandra-stress write
>Running with 8 threadCount
>
>
>Results:
>op rate                   : 25181
>partition rate            : 25181
>row rate                  : 25181
>latency mean              : 0.3
>latency median            : 0.2
>latency 95th percentile   : 0.3
>latency 99th percentile   : 0.5
>latency 99.9th percentile : 16.7
>latency max               : 331.0
>Total operation time      : 00:03:24
>
>
>gauss:~/installed/cassandra/tools/bin> ./cassandra-stress read
>Results:
>op rate                   : 35338
>partition rate            : 35338
>row rate                  : 35338
>latency mean              : 0.2
>latency median            : 0.2
>latency 95th percentile   : 0.3
>latency 99th percentile   : 0.4
>latency 99.9th percentile : 1.1
>latency max               : 17.7
>Total operation time      : 00:00:30
>
>
>
>
>Is the above result expected ?
>Thanks in advance for any suggestions !
>
>
>Shing
>
>
>
>
>


-- 

Founder/CEO Spinn3r.com

Location: San Francisco, CA

blog: http://burtonator.wordpress.com
… or check out my Google+ profile

Reply via email to