[infinispan-issues] [JBoss JIRA] (ISPN-5542) Shorten interceptor stack for local caches

[Dan Berindei (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-5542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13083020#comment-13083020 ] 

Dan Berindei commented on ISPN-5542:
------------------------------------

Ok, so you are only testing read access, and no eviction... the link I posted isn't relevant in this case.

The results were a bit lower and more tightly grouped on my machine (i7-4900MQ, OpenJDK 1.8.0_45 with {{-server -XX:+AggressiveOpts -XX:+UseCompressedOops}}):

{noformat}
Benchmark                        Mode  Cnt          Score         Error  Units
MapBenchmark.testCache          thrpt  200   11450421.970 ±   64022.513  ops/s
MapBenchmark.testChm            thrpt  200  121654143.099 ±  349886.912  ops/s
MapBenchmark.testDataContainer  thrpt  200   96444066.368 ± 1088248.658  ops/s
{noformat}

Still, it's weird how huge the difference between the CHM and DataContainer results are, considering that all {{DataContainer.get(k)}} does extra is {{if(e != null && e.canExpire())}} and that {{canExpire()}} can be replaced by the JIT with {{false}}. I really expected {{DC.get()}} to be inlined and for DC to perform exactly the same as CHM, but I guess there's still a type guard in there.

> Shorten interceptor stack for local caches
> ------------------------------------------
>
>                 Key: ISPN-5542
>                 URL: https://issues.jboss.org/browse/ISPN-5542
>             Project: Infinispan
>          Issue Type: Enhancement
>          Components: Core
>    Affects Versions: 8.0.0.Alpha1
>            Reporter: Radim Vansa
>            Assignee: Radim Vansa
>             Fix For: 8.0.0.Beta1
>
>
> Accessing local caches is much slower than plain concurrent hash maps, likely due high interceptor stack. One optimization is to have options to remove some interceptors when these are not used.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)