[
http://jira.amdatu.org/jira/browse/AMDATUCASSANDRA-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Angelo van der Sijpt reopened AMDATUCASSANDRA-51:
-------------------------------------------------
Assignee: Ivo Ladage - van Doorn (was: Angelo van der Sijpt)
I'm pretty sure the cache contains some problems (such as storing unescaped
values in cache keys), but I'm unable to write a nice (failing) test for it
since the underlying mock does not behave the way a spec-compliant useradmin
would. Can you please dig into this?
> Major performance decrease when adding/removing users
> -----------------------------------------------------
>
> Key: AMDATUCASSANDRA-51
> URL: http://jira.amdatu.org/jira/browse/AMDATUCASSANDRA-51
> Project: Amdatu Cassandra
> Issue Type: Bug
> Components: Storage implementations
> Affects Versions: 0.1.1
> Reporter: Ivo Ladage - van Doorn
> Assignee: Ivo Ladage - van Doorn
> Fix For: 0.2.0
>
>
> If you run the JMeter plans in this order, you will find that when you run
> the last plan there is a significant performance slowdown in Cassandra:
> - Amdatu Get Users - 0.1.0.jmx
> - Amdatu UserAdmin - 0.1.0.jmx for some time (i.e. 2 minutes)
> - Amdatu Get Users - 0.1.0.jmx
> Note that at this time there will only be a few users available in UserAdmin,
> still Cassandra queries on the CF Role take a very very long time. Using
> YourKit it seems that all rowkeys of previous users still exist as it is very
> busy with;
> com.google.common.base.Preconditions.checkState(boolean)
> com.google.common.collect.AbstractIterator.hasNext()
> invoked 532000 times from
> org.apache.cassandra.thrift.CassandraServer.get_range_slices(ColumnParent,
> SlicePredicate, KeyRange, ConsistencyLevel)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers
