Anyway you can test this with a 32GB heap? :)
On Wed, Jul 10, 2013 at 5:23 PM, Otis Gospodnetic < otis.gospodne...@gmail.com> wrote: > But, very importantly: > > CPU after changes: https://apps.sematext.com/spm/s/CpZ9aPhL9L > Load after changes: https://apps.sematext.com/spm/s/i7f3x6MXdZ > > So in practical terms, use something like -XX:MaxGCPauseMillis=200 > -XX:NewRatio=4 to force short GC pauses, but count on having more of > them and CPU sweating more. This gives you smaller pauses, no big STW > pauses, but be prepared to pay in CPU cycles. > > HTH > > Otis > -- > HBase Performance Monitoring -- http://sematext.com/spm > > > > On Wed, Jul 10, 2013 at 4:20 PM, Otis Gospodnetic > <otis.gospodne...@gmail.com> wrote: > > Not big in this case - 1800m > > > > Otis > > -- > > HBase Performance Monitoring -- http://sematext.com/spm > > > > > > > > On Wed, Jul 10, 2013 at 3:57 PM, Vladimir Rodionov > > <vrodio...@carrieriq.com> wrote: > >> > >> What is -Xmx heap size? > >> > >> Best regards, > >> Vladimir Rodionov > >> Principal Platform Engineer > >> Carrier IQ, www.carrieriq.com > >> e-mail: vrodio...@carrieriq.com > >> > >> ________________________________________ > >> From: Otis Gospodnetic [otis.gospodne...@gmail.com] > >> Sent: Wednesday, July 10, 2013 12:00 PM > >> To: user@hbase.apache.org > >> Subject: G1 before/after GC time graph > >> > >> Hi, > >> > >> There was talk of G1 and HBase here over the past few days. I wanted > >> to share a fresh and telling SPM graph showing G1 + some other params > >> in action: > >> > >> Result first: https://apps.sematext.com/spm/s/wN0hKVixxX > >> > >> This is what we had before: > >> -XX:+HeapDumpOnOutOfMemoryError -XX:+UseG1GC > >> -XX:InitiatingHeapOccupancyPercent=35 -XX:G1ReservePercent=25 > >> > >> And then we added: > >> -XX:MaxGCPauseMillis=200 -XX:NewRatio=4 > >> > >> I hope this helps. > >> > >> Otis > >> -- > >> HBase Performance Monitoring -- http://sematext.com/spm > >> > >> Confidentiality Notice: The information contained in this message, > including any attachments hereto, may be confidential and is intended to be > read only by the individual or entity to whom this message is addressed. If > the reader of this message is not the intended recipient or an agent or > designee of the intended recipient, please note that any review, use, > disclosure or distribution of this message or its attachments, in any form, > is strictly prohibited. If you have received this message in error, please > immediately notify the sender and/or notificati...@carrieriq.com and > delete or destroy any copy of this message and its attachments. > -- Kevin O'Dell Systems Engineer, Cloudera
