cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Berenguer Blasi (Jira)" <>
Subject [jira] [Commented] (CASSANDRA-15766) NoSpamLogger arguments building objects on hot paths
Date Tue, 14 Jul 2020 15:33:00 GMT


Berenguer Blasi commented on CASSANDRA-15766:

Yeah that one was on my list, no worries. I'll be busy a while on a 4.0 quality ticket. [~maedhroz]
feel free otherwise I'll steal it back from you when I finish lol

> NoSpamLogger arguments building objects on hot paths
> ----------------------------------------------------
>                 Key: CASSANDRA-15766
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Observability/Logging
>            Reporter: Jon Meredith
>            Assignee: Caleb Rackliffe
>            Priority: Normal
>             Fix For: 4.0-beta
> NoSpamLogger is used in hot logging paths to prevent logs being overrun.  For that to
be most effective the arguments to the logger need to be cheap to construct.  During the
internode messaging refactor CASSANDRA-15066, performance changes to BufferPool for CASSANDRA-14416
> were accidentally reverted in the merge up from 3.11.
> Reviewing other uses since, it looks like there are a few places where the arguments
require some form of String building.
> org.apache.cassandra.utils.memory.BufferPool.GlobalPool#allocateMoreChunks
> Formatting arguments should either be precomputed, or if expensive they should be computed
after the decision on whether to noSpamLog has been made.

This message was sent by Atlassian Jira

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message