Github user jloisel commented on the issue:
https://github.com/apache/jmeter/pull/221
> Why do you think synchronized CSS cache is the bottleneck then?
I saw a race condition in the existing implementation and fixed it
following the [Boy scouts
principle](http://programmer.97things.oreilly.com/wiki/index.php/The_Boy_Scout_Rule).
It's simply not working properly: the CPU can go crazy if the cache is full
when many virtual users are executing. If the requirement is that the code
doesn't need to work, then sure, I can make an implementation that gives
instant results.
Anyway, I'll be okay with any decision being made, I'm not getting any
reward for pushing Guava inside JMeter :+1:
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
