cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jaroslav Kamenik (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-8231) Wrong size of cached prepared statements
Date Fri, 31 Oct 2014 14:04:33 GMT
Jaroslav Kamenik created CASSANDRA-8231:
-------------------------------------------

             Summary: Wrong size of cached prepared statements
                 Key: CASSANDRA-8231
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8231
             Project: Cassandra
          Issue Type: Bug
          Components: Core
            Reporter: Jaroslav Kamenik


Cassandra counts memory footprint of prepared statements for caching purposes. It seems, that
there is problem with some statements, ie SelectStatement. Even simple selects is counted
as 100KB object, updates, deletes etc have few hundreds or thousands bytes. Result is that
cache - QueryProcessor.preparedStatements  - holds just fraction of statements..

I dig a little into the code, and it seems that problem is in jamm in class MemoryMeter. It
seems that if instance contains reference to class, it counts size of whole class too. SelectStatement
references EnumSet through ResultSet.Metadata and EnumSet holds reference to Enum class...





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

Mime
View raw message