See tserver.total.mutation.queue.max=50M (default)
Previously, the amount of memory used by a tabletserver with concurrent
write requests could exceed this value (as the configuration was per
write session instead of per tabletserver).
You can also try setting the table's durability from sync to flush which
will have a large increase in performance. Additionally, you can disable
GZ compression for the table.
dlmar...@comcast.net wrote:
I don't remember seeing anything about native library performance improvement,
but I do know that there has been talk of a performance regression in Accumulo
1.7.0 using the default configuration. I don't remember the specific details
off-hand, but it had something to do with the default value of a property
changing.
-----Original Message-----
From: Brown, Scott M (IS) [mailto:scott.bro...@ngc.com]
Sent: Wednesday, October 19, 2016 6:49 PM
To: user@accumulo.apache.org
Subject: 1.7 native library performance boost
So with 1.7, we noticed the statement that utilizing the native library can add
up to 40% performance increase. With two identical systems, one with 1.6
one with 1.7, we're not seeing any notable difference at all with either
queries or large ingests.
Any idea what operations can take advantage, or what circumstances the
performance boost comes into play?
