[Webkit-unassigned] [Bug 204398] [Win] Use thread_local to hold Ref<WTF::Thread> in the thread rather than using FLS

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=204398

--- Comment #5 from Fujii Hironori <Hironori.Fujii at sony.com> ---
https://chromium.googlesource.com/chromium/src/+/e8f14977868c566c4d00666db010d1255e931c86
https://chromium-review.googlesource.com/c/chromium/src/+/1873751

> thread_local is already used in Chrome, though not widely as it is still banned
> by the style-guide. Add a benchmark to estimate its performance.
> 
> Detailed results below, tldr:
> - On Linux: 2-3x faster than the current TLS implementation for reading, ~10x
>   faster for writing
> - On Android: ~4x faster for reading
> 
(...)

Re: [chromium-dev] Using C++11 thread_local storage class
https://groups.google.com/a/chromium.org/d/msg/cxx/h7O5BdtWCZw/NUhcP-DBBwAJ

https://groups.google.com/a/chromium.org/d/msg/cxx/h7O5BdtWCZw/Pa8v7RFBCAAJ

> I've done some performance comparisons between using thread_local
> and using WTF::ThreadSpecific, and there's a 2.5x performance
> improvement[1] on both Windows and Mac. The generated code is
> also significantly smaller, which is a nice benefit as well.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20191202/04bdb1ee/attachment.htm>