You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Dmitry Konstantinov (Jira)" <ji...@apache.org> on 2026/05/20 19:57:00 UTC

[jira] [Updated] (CASSANDRA-21020) Optimize thread local for metrics and tracing

     [ 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.x
                   7.x

> 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.x, 7.x
>
>          Time Spent: 10m
>  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: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org