aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mehrdad Nurolahzade (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (AURORA-1865) Experiment with Increasing H2 QUERY_CACHE_SIZE
Date Wed, 21 Dec 2016 17:11:58 GMT

     [ https://issues.apache.org/jira/browse/AURORA-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mehrdad Nurolahzade closed AURORA-1865.
---------------------------------------
    Resolution: Duplicate

> Experiment with Increasing H2 QUERY_CACHE_SIZE
> ----------------------------------------------
>
>                 Key: AURORA-1865
>                 URL: https://issues.apache.org/jira/browse/AURORA-1865
>             Project: Aurora
>          Issue Type: Story
>          Components: Scheduler
>            Reporter: Mehrdad Nurolahzade
>            Priority: Minor
>
> Aurora scheduler is not setting a value for {{QUERY_CACHE_SIZE}}, therefore it is relying
on H2's default cache size of 8 statements. There might be potential performance gain from
increasing H2 query cache size ([example discussion thread|https://groups.google.com/forum/#!topic/h2-database/pGG9HA5ckhw]).
> Looking at execution count of queries (in {{INFORMATION_SCHEMA.QUERY_STATISTICS}} meta
table), selecting host attributes query is repeated 2-3 orders of magnitude more than other
queries, giving it a substantial cumulative execution cost. Scheduler needs to ensure all
such high frequency statements are always cached.
> Verify if increasing {{QUERY_CACHE_SIZE}} positively impacts scheduler performance.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message