[infinispan-issues] [JBoss JIRA] (ISPN-2707) Trace log in EntryWrappingInterceptor could deteriorate performance

[Radim Vansa (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-2707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Radim Vansa updated ISPN-2707:
------------------------------

    Description: 
In {{EntryWrappingInterceptor.visitInvalidateL1Command}} there is a trace log which does not check if the trace is enabled - with invalidate command with a lot of keys (such as in case of ST) this would construct for each of these keys really long strings (with all the keys...), and then throw it off.

Moreover, the InvalidateL1Command is still built even if I don't have L1 enabled, but that's another issue.

  was:
In {{EntryWrappingInterceptor.visitInvalidateL1Command}} there is a trace log which does not check if the trace is enabled - with invalidate command with a lot of keys (such as in case of ST) this can construct many really long strings, for each of these keys and then throw it off.

Moreover, the InvalidateL1Command is still built even if I don't have L1 enabled, but that's another issue.


    
> Trace log in EntryWrappingInterceptor could deteriorate performance
> -------------------------------------------------------------------
>
>                 Key: ISPN-2707
>                 URL: https://issues.jboss.org/browse/ISPN-2707
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Distributed Cache
>    Affects Versions: 5.2.0.CR1
>            Reporter: Radim Vansa
>            Assignee: Mircea Markus
>
> In {{EntryWrappingInterceptor.visitInvalidateL1Command}} there is a trace log which does not check if the trace is enabled - with invalidate command with a lot of keys (such as in case of ST) this would construct for each of these keys really long strings (with all the keys...), and then throw it off.
> Moreover, the InvalidateL1Command is still built even if I don't have L1 enabled, but that's another issue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira