-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Carsten,
> In this regard, what I personally miss in Mikios - however nice - analysis,
> is what are the effects on the application stop times due to any garbage
> collection runs for the cases tested. In most cases, I prefer having low
> pauses
On Mon, Aug 30, 2010 at 5:18 PM, Peter Schuller
wrote:
> Has anyone run Cassandra with G1 in production for prolonged periods
> of time?
Not AFAIK.
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of Riptano, the source for professional Cassandra support
http://riptano.com
> collection runs for the cases tested. In most cases, I prefer having low
> pauses due to any garbage collection runs and don't care too much about the
> shape of the memory usage, and I guess, that's the reason why the low pause
> collector is used by default for running cassandra. For myself, I
On Sun, Aug 29, 2010 at 1:53 PM, Carsten Krebs wrote:
>
>
> Also, note that lack of saw-toothing is not a goal in and of itself
> and may even be bad. For example, with respect to the young generation
> the situation is essentially:
>
> (1) The larger the young generation, the more significant the
>
> Also, note that lack of saw-toothing is not a goal in and of itself
> and may even be bad. For example, with respect to the young generation
> the situation is essentially:
>
> (1) The larger the young generation, the more significant the saw-tooth.
> (2) The larger the young generation, the
> Before I applied these changes the young gen and the survivor space
> were very spiky. Now they both seem very low all the time. As you see
> from my screen shot, before these changes my JVM memory would make
> large saw tooths, now all three pools young, eden, perm seem smoother.
I'm not sure w
On Fri, Aug 27, 2010 at 6:49 PM, Jonathan Ellis wrote:
> I supsect something else is making the difference for ecapriolo. The
> documentation says,
>
> The incremental mode is meant to lessen the impact of long concurrent
> phases by periodically stopping the concurrent phase to yield back the
>
I supsect something else is making the difference for ecapriolo. The
documentation says,
The incremental mode is meant to lessen the impact of long concurrent
phases by periodically stopping the concurrent phase to yield back the
processor to the application. [Remember, "concurrent" means "not
bl
ecapriolo's testing seemed to indicate it _did_ change the behavior.
wonder what the difference is?
On Fri, Aug 27, 2010 at 6:23 AM, Mikio Braun wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Dear all,
>
> thanks for your comments, and I'm glad that you found my post helpful.
>
> Co
about a month. it's not like this is a difficult change to apply yourself.
On Fri, Aug 27, 2010 at 1:43 AM, David Dabbs wrote:
>>Jonathan Ellis
>>
>>added CMSInitiatingOccupancyFraction=80 for 0.6.6 and 0.7beta2
>
> When do you expect 0.6.6 to land?
>
>
> Thanks,
>
> David
>
>
>
--
Jonathan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear all,
thanks for your comments, and I'm glad that you found my post helpful.
Concerning the incremental CMS, I've recently updated my post and added
the experiments repeated on one of our cluster nodes, and for some
reason incremental CMS doesn't
> Whether or not this is likely to happen with Cassandra I don't know. I
> don't know much about the incremental duty cycles are scheduled and it
> may be the case that Cassandra is not even remotely close to having a
> problem with incremental mode.
I should further weaken my statement by pointin
> Any reason not to add the incremental mode settings? It's unusual to
> see a Cassandra node out of CPU, but wild heap oscillations are pretty
> common.
FWIW, while I have never tried it with Cassandra, the CMS incremental
mode has never ever worked well for me when I have applied it to
anything
Any reason not to add the incremental mode settings? It's unusual to
see a Cassandra node out of CPU, but wild heap oscillations are pretty
common.
On Thu, Aug 26, 2010 at 8:54 PM, Jonathan Ellis wrote:
> added CMSInitiatingOccupancyFraction=80 for 0.6.6 and 0.7beta2
>
> On Thu, Aug 26, 2010 at
>Jonathan Ellis
>
>added CMSInitiatingOccupancyFraction=80 for 0.6.6 and 0.7beta2
When do you expect 0.6.6 to land?
Thanks,
David
added CMSInitiatingOccupancyFraction=80 for 0.6.6 and 0.7beta2
On Thu, Aug 26, 2010 at 9:57 PM, Benjamin Black wrote:
> imo, these should be part of the defaults.
>
> On Tue, Aug 24, 2010 at 8:29 AM, Mikio Braun wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Dear all,
>>
>> tha
imo, these should be part of the defaults.
On Tue, Aug 24, 2010 at 8:29 AM, Mikio Braun wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Dear all,
>
> thanks again for all the comments I got on my last post. I've played a
> bit with different GC settings and got my Cassandra instance
On Tue, Aug 24, 2010 at 11:29 AM, Mikio Braun wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Dear all,
>
> thanks again for all the comments I got on my last post. I've played a
> bit with different GC settings and got my Cassandra instance to run
> very nicely with 8GB of heap.
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dear all,
thanks again for all the comments I got on my last post. I've played a
bit with different GC settings and got my Cassandra instance to run
very nicely with 8GB of heap.
I summarized my experiences with GC tuning in this follow-up post:
htt
19 matches
Mail list logo
