[
https://issues.apache.org/jira/browse/PHOENIX-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl updated PHOENIX-3064:
-----------------------------------
Attachment: PhoenixGetTableAndARRQ.png
Image of profiler session.
Can we update the client cache lazily? It seems we're forcing an update of
_every single_ query!
[~giacomotaylor], is that possible? What would the lazy conditions be? We
already do that when the table can't be found. What about columns? Can we
reliably detect an out of date cached schema and then update the cache? That
would save a lot of CPU time on the client.
> Reduce client time spent in createTableRef and ARRQ for point queries
> ----------------------------------------------------------------------
>
> Key: PHOENIX-3064
> URL: https://issues.apache.org/jira/browse/PHOENIX-3064
> Project: Phoenix
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Attachments: PhoenixGetTableAndARRQ.png
>
>
> Did some profiling for point queries (I actually wanted to test the HBase
> server side).
> I found that a _lot_ of client time is spent in
> FromCompiler.getResolverForQuery (in createTableRef) and also in
> AbstractRoundRobinQueue.offer.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
