https://bugs.documentfoundation.org/show_bug.cgi?id=130795
--- Comment #27 from Luboš Luňák <[email protected]> --- That said, looking at the profiling of the comment #25 code, the majority of time spent there is not spent actually uppercasing the string, it's spent in lock contention and the i18n classes repeatedly updating their internal state. Without that, it seems the performance would be about the same. So the reason why the SharedStringPool version is faster is because our i18n code is dumb (at least as far as performance goes) and usage of libcuckoo removes these problems from SharedStringPool, not because using SharedStringPool be inherently faster here. But I don't think I'll have the time to try to redesign the i18n code or look into why ValidQuery() gets called so often. -- You are receiving this mail because: You are the assignee for the bug.
