[
https://issues.apache.org/jira/browse/HBASE-1741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell resolved HBASE-1741.
-----------------------------------
Resolution: Fixed
Fix Version/s: (was: 0.21.0)
With the exception of the hot cell cache, the above has been accomplished.
bq. Profile and tune the servlet.
I ported PE to httpclient and profiled both client and server side with
jprofiler. There were no glaring hot spots or apparent performance problems
suitable for opening jiras for. Bulk of time is spent in I/O to client or HBase
cluster, as it should be. Overheads of Jetty and Jersey are out of scope, but
was a few % for each typically.
bq. Profile and tune the Client package. Insure that it is using Commons
HttpClient in a manner that could achieve good performance.
To the extent httpclient 3.1 is tunable, that has been done.
> [stargate] performance tuning
> -----------------------------
>
> Key: HBASE-1741
> URL: https://issues.apache.org/jira/browse/HBASE-1741
> Project: Hadoop HBase
> Issue Type: Improvement
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Priority: Minor
>
> Improve Stargate performance.
> Profile and tune the servlet.
> Profile and tune the Client package. Insure that it is using Commons
> HttpClient in a manner that could achieve good performance.
> Consider a hot cell and/or query cache backed by an LruHashMap.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
