You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jeff Jirsa (JIRA)" <ji...@apache.org> on 2018/05/12 15:43:00 UTC
[jira] [Updated] (CASSANDRA-14416) Remove string formatting lines
from hot path
[ https://issues.apache.org/jira/browse/CASSANDRA-14416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Jirsa updated CASSANDRA-14416:
-----------------------------------
Resolution: Fixed
Reviewer: Marcus Eriksson
Fix Version/s: (was: 3.11.x)
(was: 4.x)
3.11.3
4.0
Status: Resolved (was: Ready to Commit)
Better. Committed as 28058608f13d2a5bbc0da2af344b92d3acad7e26
> Remove string formatting lines from hot path
> --------------------------------------------
>
> Key: CASSANDRA-14416
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14416
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Jeff Jirsa
> Assignee: Jeff Jirsa
> Priority: Minor
> Labels: performance
> Fix For: 4.0, 3.11.3
>
>
> In the BufferPool, we have a {{NoSpamLogger}} that gets called in some conditions (like when we're at or near the cap in a given pool), which has some string formatting on it. In situations where that log line is invoked, that string formatting gets called before the rate limiting, which becomes expensive.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org