[
https://issues.apache.org/jira/browse/CASSANDRA-21020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitry Konstantinov updated CASSANDRA-21020:
--------------------------------------------
Fix Version/s: 6.0-alpha2
7.0
(was: 6.x)
(was: 7.x)
Source Control Link:
https://github.com/apache/cassandra/commit/72d53e3919ff586c507aded1d7324deab9f315c6
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Optimize thread local for metrics and tracing
> ---------------------------------------------
>
> Key: CASSANDRA-21020
> URL: https://issues.apache.org/jira/browse/CASSANDRA-21020
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Observability/Metrics, Observability/Tracing
> Reporter: Dmitry Konstantinov
> Assignee: Dmitry Konstantinov
> Priority: Normal
> Fix For: 6.0-alpha2, 7.0
>
> Attachments: CASSANDRA-21020-6.0_ci_summary.htm.zip,
> CASSANDRA-21020-trunk_ci_summary.htm.zip
>
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> Currently Netty thread local logic is used in tracing to keep state and in
> metrics (thread local counters logic introduced in CASSANDRA-20250), so we do
> the thread local lookups many times during a request processing. These cases
> can be optimized by placing these objects as field variables to Thread itself
> by introducing CassandraThread as a child of FastThreadLocalThread.
> Similar idea can be found even in JDK (ThreadLocalRandom logic was introduced
> for ForkJoinPool speedup)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
