[wp-trac] [WordPress Trac] #18007: is_serialized trouble for multibytes encoding
WordPress Trac
wp-trac at lists.automattic.com
Tue Oct 9 16:18:03 UTC 2012
#18007: is_serialized trouble for multibytes encoding
---------------------------------+-----------------------------
Reporter: challet | Owner:
Type: defect (bug) | Status: new
Priority: normal | Milestone: Future Release
Component: Charset | Version: 3.2
Severity: normal | Resolution:
Keywords: has-patch 3.6-early |
---------------------------------+-----------------------------
Comment (by SergeyBiryukov):
More takes in [attachment:18007.4.patch], [attachment:18007.5.patch] and
[attachment:18007.5.alt.patch].
I didn't test all the cases yesterday, here's the full table. Increased
the number of iterations to 10,000,000 to make the results more accurate.
||`mbstring.func_overload` off||`mbstring.func_overload` on||
||62,783s — unpatched||36,596s — unpatched||
||63,268s — [attachment:18007.5.patch]||67,948s —
[attachment:18007.5.patch]||
||64,873s — [attachment:18007.2.patch]||75,975s —
[attachment:18007.2.patch]||
||71,176s — [attachment:18007.4.patch]||76,906s —
[attachment:18007.5.alt.patch]||
||73,531s — [attachment:18007.3.patch]||86,326s —
[attachment:18007.4.patch]||
||76,352s — [attachment:18007.5.alt.patch]||88,115s —
[attachment:18007.3.patch]||
||99,088s — [attachment:18007.2.alt.patch]||100,632s —
[attachment:18007.2.alt.patch]||
It turned out that [attachment:18007.2.patch] is actually faster than
[attachment:18007.3.patch] in both cases. [attachment:18007.5.patch] shows
the best performance, but probably looks less obvious.
Not sure why the unpatched results differ by 75%, but the difference is
consistent after several takes.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/18007#comment:10>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list