[
https://issues.apache.org/jira/browse/CASSANDRA-11555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15266672#comment-15266672
]
Robert Stupp commented on CASSANDRA-11555:
------------------------------------------
Tests look good.
I've applied the first issue. {{FileUtils.MB}} is a {{private static double}},
so I left it as it is.
Would you be fine with [this
log|https://github.com/apache/cassandra/compare/trunk...snazy:11555-pstmt-cache-config-trunk#diff-9c19942eca6c858baad84e942b3c7e21R133]
message, too?
> Make prepared statement cache size configurable
> -----------------------------------------------
>
> Key: CASSANDRA-11555
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11555
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL
> Reporter: Robert Stupp
> Assignee: Robert Stupp
> Priority: Minor
> Labels: docs-impacting
> Fix For: 3.x
>
>
> 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)
