>
> If you are using the off heap cache the upper bound is memory. If you are
> using the on head it's the JVM heap.
But as I said earlier, I could not watch the usage of JVM heap while
reading saved caches
AM, Wei Zhu wrote:
>
>> Just curious why do you think row key will take 300 byte? If the row key is
>> Long type, doesn't it take 8 bytes?
>> In his case, the rowCache was 500M with 1.6M rows, so the row data is 300B.
>> Did I miss something?
>>
>>
y
> is Long type, doesn't it take 8 bytes?
> In his case, the rowCache was 500M with 1.6M rows, so the row data is
> 300B. Did I miss something?
>
> Thanks.
> -Wei
>
> ----------
> *From:* aaron morton
> *To:* user@cassandra.apache.org
> *Se
ton
> To: user@cassandra.apache.org
> Sent: Thursday, November 15, 2012 12:15 PM
> Subject: Re: unable to read saved rowcache from disk
>
> For a row cache of 1,650,000:
>
> 16 byte token
> 300 byte row key ?
> and row data ?
> multiply by a java fudg
user@cassandra.apache.org
Sent: Thursday, November 15, 2012 12:15 PM
Subject: Re: unable to read saved rowcache from disk
For a row cache of 1,650,000:
16 byte token
300 byte row key ?
and row data ?
multiply by a java fudge factor or 5 or 10.
Trying delete the saved cache and restarting.
C
ache was not updated? Could be something else eats up the memory. You may
> profile memory and see who consumes the memory.
>
>
> Thanks.
> -Wei
>
> Sent from my Samsung smartphone on AT&T
>
>
> Original message ----
> Subject: Re: unable to
gt; Sent from my Samsung smartphone on AT&T
>
>
> ---- Original message ----
> Subject: Re: unable to read saved rowcache from disk
> From: Manu Zhang
> To: user@cassandra.apache.org
> CC:
>
>
> 3G, other jvm parameters are unchanged.
>
>
> On
. You may
profile memory and see who consumes the memory.
Thanks.
-Wei
Sent from my Samsung smartphone on AT&T
Original message
Subject: Re: unable to read saved rowcache from disk
From: Manu Zhang
To: user@cassandra.apache.org
CC:
3G, other jvm parameters are uncha
this?
>>
>>
>> Thanks.
>> -Wei
>>
>> Sent from my Samsung smartphone on AT&T
>>
>>
>> Original message
>> Subject: Re: unable to read saved rowcache from disk
>> From: Manu Zhang
>> To: user@cassandra.apache.org
>> CC:
>&
How big is your heap? Did you change the jvm parameter?
Thanks.
-Wei
Sent from my Samsung smartphone on AT&T
Original message
Subject: Re: unable to read saved rowcache from disk
From: Manu Zhang
To: user@cassandra.apache.org
CC:
add a counter and print out my
add a counter and print out myself
On Thu, Nov 15, 2012 at 1:51 PM, Wz1975 wrote:
> Curious where did you see this?
>
>
> Thanks.
> -Wei
>
> Sent from my Samsung smartphone on AT&T
>
>
> Original message ----
> Subject: Re: unable to read
Curious where did you see this?
Thanks.
-Wei
Sent from my Samsung smartphone on AT&T
Original message
Subject: Re: unable to read saved rowcache from disk
From: Manu Zhang
To: user@cassandra.apache.org
CC:
OOM at deserializing 747321th row
On Thu, Nov 15, 2012
;s about right...
>> So for 15MB, there could be a lot of "narrow" rows. (if the key is Long,
>> could be more than 1M rows)
>>
>> Thanks.
>> -Wei
>> ----------
>> *From:* Edward Capriolo
>> *To:* user@cassandra.apach
-Wei
> --
> *From:* Edward Capriolo
> *To:* user@cassandra.apache.org
> *Sent:* Tuesday, November 13, 2012 11:13 PM
> *Subject:* Re: unable to read saved rowcache from disk
>
> http://wiki.apache.org/cassandra/LargeDataSetConsiderations
>
> A negative side-
is Long, could
be more than 1M rows)
Thanks.
-Wei
From: Edward Capriolo
To: user@cassandra.apache.org
Sent: Tuesday, November 13, 2012 11:13 PM
Subject: Re: unable to read saved rowcache from disk
http://wiki.apache.org/cassandra/LargeDataSetConsiderati
actually, I'm thinking about a bug or something
On Wed, Nov 14, 2012 at 3:13 PM, Edward Capriolo wrote:
> http://wiki.apache.org/cassandra/LargeDataSetConsiderations
>
> A negative side-effect of a large row-cache is start-up time. The
> periodic saving of the row cache information only saves th
http://wiki.apache.org/cassandra/LargeDataSetConsiderations
A negative side-effect of a large row-cache is start-up time. The
periodic saving of the row cache information only saves the keys that
are cached; the data has to be pre-fetched on start-up. On a large
data set, this is probably going to
"incorrect"... what do you mean? I think it's only 15MB, which is not big.
On Wed, Nov 14, 2012 at 10:38 AM, Edward Capriolo wrote:
> Yes the row cache "could be" incorrect so on startup cassandra verify they
> saved row cache by re reading. It takes a long time so do not save a big
> row cache.
Yes the row cache "could be" incorrect so on startup cassandra verify they
saved row cache by re reading. It takes a long time so do not save a big
row cache.
On Tuesday, November 13, 2012, Manu Zhang wrote:
> I have a rowcache provieded by SerializingCacheProvider.
> The data that has been read
19 matches
Mail list logo
