[ https://issues.apache.org/jira/browse/CASSANDRA-14436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16474788#comment-16474788 ]
Chris Lohfink edited comment on CASSANDRA-14436 at 5/14/18 8:58 PM: -------------------------------------------------------------------- new samplers: cas contentiion, read query, mutation size. With all samplers enabled, atleast on laptop cassandra-stress shows no detectable difference between when profiling and normal. I would suspect a difference on larger systems with highly concurrent reads, with contention on putting the samples on the queue. If concerned though can just run for 1 second or not run it though (like enabling probabilistic tracing, but with significantly less cost). was (Author: cnlwsu): new samplers: cas contentiion, read query, mutation size > Add sampler for query time and expose with nodetool > --------------------------------------------------- > > Key: CASSANDRA-14436 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14436 > Project: Cassandra > Issue Type: Improvement > Reporter: Chris Lohfink > Assignee: Chris Lohfink > Priority: Major > > Create a new {{nodetool profileload}} that functions just like toppartitions > but with more data, returning the slowest local reads and writes on the host > during a given duration and highest frequency touched partitions (same as > {{nodetool toppartitions}}). Refactor included to extend use of the sampler > for uses outside of top frequency (max instead of total sample values). > Future work to this is to include top cpu and allocations by query and > possibly tasks/cpu/allocations by stage during time window. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org