difference to get 1 at a time,
or get 100 at a time. Since the result set is exactly same.
By the way: the Jassandra you are using is updated for the issue you raised.
Now, the result set from select is sorted.
Thanks,
Regards,
dop
From: Caribbean410 [mailto:caribbean...@gmail.com]
Sent
at 6:13 PM, Caribbean410
wrote:
> Hi,
>
> I wrote 200k records to db with each record 5MB. Get this error when I
uses
> 3 threads (each thread tries to read 200k record totally, 100 records a
> time) to read data from db. The write is OK, the error comes from read.
> Right
heap space
if you are reading 500MB per thrift request from each of 3 threads,
then yes, simple arithmetic indicates that 1GB heap is not enough.
On Mon, Jun 14, 2010 at 6:13 PM, Caribbean410
wrote:
> Hi,
>
> I wrote 200k records to db with each record 5MB. Get this error when I
uses
>
ove some unnecessary column family and change the
> size of rowcache and keycache, now the latency changes from 0.25ms to
> 0.09ms. In essence 0.09ms*200k=18s.”, it still takes 400 seconds to
> returning?
>
>
>
> *From:* Caribbean410 [mailto:caribbean...@gmail.com]
>
Hi,
I wrote 200k records to db with each record 5MB. Get this error when I uses
3 threads (each thread tries to read 200k record totally, 100 records a
time) to read data from db. The write is OK, the error comes from read.
Right now the Xmx of JVM is 1GB. I changed it to 2GB, still not working. I
, it still takes 400 seconds to
returning?
From: Caribbean410 [mailto:caribbean...@gmail.com]
Sent: Saturday, June 12, 2010 8:48 AM
To: user@cassandra.apache.org
Subject: Re: read operation is slow
Hi, do you mean this one should not introduce much extra delay? To read a
record, I need select
*200k=18s.”, it still takes 400 seconds to
> returning?
>
>
>
> *From:* Caribbean410 [mailto:caribbean...@gmail.com]
> *Sent:* Saturday, June 12, 2010 8:48 AM
>
> *To:* user@cassandra.apache.org
> *Subject:* Re: read operation is slow
>
>
>
> Hi, do you mean this on
; The select here basically is a call to Thrift API: get_range_slices
>
>
>
>
>
> *From:* Caribbean410 [mailto:caribbean...@gmail.com]
> *Sent:* Saturday, June 12, 2010 8:00 AM
>
> *To:* user@cassandra.apache.org
> *Subject:* Re: read operation is slow
>
>
at the latency is internal to
> cassandra, vs what your client is introducing
>
> then you should probably read the comments in the configuration file
> about caching
>
> On Fri, Jun 11, 2010 at 9:38 AM, Caribbean410
> wrote:
> >
> > Thanks Riyad.
> >
>
; about caching
>
> On Fri, Jun 11, 2010 at 9:38 AM, Caribbean410
> wrote:
> >
> > Thanks Riyad.
> >
> > Right now I am just testing Cassandra on single node. The server and
> client
> > are running on the same machine. I tried the read test again on two
> &g
at 8:19 AM, Riyad Kalla wrote:
> Caribbean410,
>
> This comes up on the Redis list alot as well -- what you are actually
> measuring is the client sending a network connection to the Cas server and
> it replying -- so the performance numbers you are getting can easily be 70%
>
Hello,
I am testing the performance of cassandra. We write 200k records to
database and each record is 1k size. Then we read these 200k records.
It takes more than 400s to finish the read which is much slower than
mysql (20s around). I read some discussion online and someone suggest
to make multip
12 matches
Mail list logo
