[
https://issues.apache.org/jira/browse/CASSANDRA-11555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Stupp updated CASSANDRA-11555:
-------------------------------------
Status: Patch Available (was: Open)
[branch|https://github.com/apache/cassandra/compare/trunk...snazy:11555-pstmt-cache-config-trunk]
[testall|http://cassci.datastax.com/view/Dev/view/snazy/job/snazy-11555-pstmt-cache-config-trunk-testall/lastBuild/]
[dtest|http://cassci.datastax.com/view/Dev/view/snazy/job/snazy-11555-pstmt-cache-config-trunk-dtest/lastBuild/]
> Make prepared statement cache size configurable
> -----------------------------------------------
>
> Key: CASSANDRA-11555
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11555
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Robert Stupp
> Assignee: Robert Stupp
> Priority: Minor
>
> The prepared statement caches in {{org.apache.cassandra.cql3.QueryProcessor}}
> are configured using the formula {{Runtime.getRuntime().maxMemory() / 256}}.
> Sometimes applications may need more than that. Proposal is to make that
> value configurable - probably also distinguish thrift and native CQL3 queries
> (new applications don't need the thrift stuff).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
