[slf4j-dev] [Bug 298] locks around logger maps inhibit concurrency

[bugzilla-daemon at qos.ch]

http://bugzilla.slf4j.org/show_bug.cgi?id=298

--- Comment #4 from Taras Tielkes <taras.tielkes at gmail.com> 2013-03-25 00:09:34 CET ---
The changes themselves are indeed quite simple.
I'd be happy to (figure out how to) create a github pull request.

Some additional comments:
* I've been using YourKit 12 (on Java 7, Linux x64) for profiling, using the
"sampling" mode.
* It's quite likely that the profiling agent does have an impact on the
measurements. All lock contention we've found with YourKit over the last couple
of years has been quite reliable/correct though.
* I'll chat with the YourKit guys to see if they have any feedback on what I'm
observing.
* I have not yet done a re-profile with a patched slf4j yet. I'll do this in
the coming days (I'll need to patch the slf4j version inside the JBoss release
we're using).
* ConcurrentHashMap (versus a plain HashMap or Hashtable) does come with a
higher memory overhead per entry. In this particular use case I would  not
expect any excesses.

-- 
Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.