bschoening commented on code in PR #3917: URL: https://github.com/apache/cassandra/pull/3917#discussion_r2045819163
########## doc/modules/cassandra/pages/cql/cql_singlefile.adoc: ########## @@ -239,6 +239,20 @@ provide values for `LIMIT`, `TIMESTAMP`, and `TTL` clauses. If anonymous bind markers are used, the names for the query parameters will be `[limit]`, `[timestamp]`, and `[ttl]`, respectively. +Prepared Statements are cached by cassandra in-memory which can be Review Comment: @tolbertam that's helpful, but until I looked carefully at the code it wasn't clear what the eviction policy was (LRU?) or if bad statements (i.e, not correctly qualified) will eventually be evicted or not. Mentioning Caffeine and the eviction policy used. How about something like this: "To ensure optimal performance, it's important to use bind markers '?' for all non-constant values in your SQL statements. If you include literal values directly in the query instead, each variation will be treated as a unique statement that must be prepared and cached separately. When the Caffeine-managed cache reaches its maximum size, older or less frequently used statements are evicted, leading to additional overhead as previously prepared statements must be re-prepared." -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: pr-unsubscr...@cassandra.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: pr-unsubscr...@cassandra.apache.org For additional commands, e-mail: pr-h...@cassandra.apache.org
