Re: Performance oddity between AWS instance sizes

2014-09-19 Thread Otis Gospodnetic
Hi, The oddity in this thread is that there is no mention of metrics (sorry if I missed them being mentioned!). For example, that 1GB heap makes me think a graph showing JVM heap memory pool sizes/utilization and GC counts/times would quickly tell us/you if you are simply not giving the JVM enoug

Re: Performance oddity between AWS instance sizes

2014-09-19 Thread Andrew Purtell
FWIW, I pushed a fix for that NPE On Fri, Sep 19, 2014 at 9:13 AM, Andrew Purtell wrote: > Thanks for trying the new client out. Shame about that NPE, I'll look into it. > > > >> On Sep 18, 2014, at 8:43 PM, Josh Williams wrote: >> >> Hi Andrew, >> >> I'll definitely bump up the heap on subsequ

Re: Performance oddity between AWS instance sizes

2014-09-19 Thread Andrew Purtell
Thanks for trying the new client out. Shame about that NPE, I'll look into it. > On Sep 18, 2014, at 8:43 PM, Josh Williams wrote: > > Hi Andrew, > > I'll definitely bump up the heap on subsequent tests -- thanks for the > tip. It was increased to 8 GB, but that didn't make any difference fo

Re: Performance oddity between AWS instance sizes

2014-09-18 Thread Josh Williams
Hi Andrew, I'll definitely bump up the heap on subsequent tests -- thanks for the tip. It was increased to 8 GB, but that didn't make any difference for the older YCSB. Using your YCSB branch with the updated HBase client definitely makes a difference, however, showing consistent throughput for

Re: Performance oddity between AWS instance sizes

2014-09-18 Thread Andrew Purtell
1 GB heap is nowhere enough to run if you're tying to test something real (or approximate it with YCSB). Try 4 or 8, anything up to 31 GB, use case dependent. >= 32 GB gives away compressed OOPs and maybe GC issues. Also, I recently redid the HBase YCSB client in a modern way for >= 0.98. See http

Re: Performance oddity between AWS instance sizes

2014-09-18 Thread Josh Williams
Ted, Stack trace, that's definitely a good idea. Here's one jstack snapshot from the region server while there's no apparent activity going on: https://gist.github.com/joshwilliams/4950c1d92382ea7f3160 If it's helpful, this is the YCSB side of the equation right around the same time: https://gis

Re: Performance oddity between AWS instance sizes

2014-09-18 Thread Gary Helmling
What do you have HBASE_HEAPSIZE set to in hbase-env.sh? Is it possible that you're overcommitting memory and the instance is swapping? Just a shot in the dark, but I see that the m3.2xlarge instance has 30G of memory vs. 15G for c3.2xlarge. On Wed, Sep 17, 2014 at 3:28 PM, Ted Yu wrote: > bq. t

Re: Performance oddity between AWS instance sizes

2014-09-17 Thread Ted Yu
bq. there's almost no activity on either side During this period, can you capture stack trace for the region server and pastebin the stack ? Cheers On Wed, Sep 17, 2014 at 3:21 PM, Josh Williams wrote: > Hi, everyone. Here's a strange one, at least to me. > > I'm doing some performance profil

Performance oddity between AWS instance sizes

2014-09-17 Thread Josh Williams
Hi, everyone. Here's a strange one, at least to me. I'm doing some performance profiling, and as a rudimentary test I've been using YCSB to drive HBase (originally 0.98.3, recently updated to 0.98.6.) The problem happens on a few different instance sizes, but this is probably the closest compari