On 8/30/2010 7:44 AM, Martin [gz] wrote:
> Okay, I'm confused now. Every microbenchmark I could cook up the bzrlib version of the _escape_cdata is actually slower than the original. So, I tried profiling bundle, and sure enough there's an xml escaping function high up in the list, but it's not the etree one:
>
> 502 0 205.1471 16.3189 <C:\Python24\Lib\site-packages\bzrlib\xml8.py>:217(write_inventory)
> +2610268 0 13.1339 8.5832 +<C:\Python24\Lib\site-packages\bzrlib\xml8.py>:94(_encode_and_escape)
>
> So, what command can I run instead to measure how much ripping this code out hurts performance?
Note also that when we performance tuned it, we may have been running
under lsprof, which would also penalize the extra function calls more
than real runtime would (IME).
John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 8/30/2010 7:44 AM, Martin [gz] wrote: Lib\site- packages\ bzrlib\ xml8.py> :217(write_ inventory) Lib\site- packages\ bzrlib\ xml8.py> :94(_encode_ and_escape)
> Okay, I'm confused now. Every microbenchmark I could cook up the bzrlib version of the _escape_cdata is actually slower than the original. So, I tried profiling bundle, and sure enough there's an xml escaping function high up in the list, but it's not the etree one:
>
> 502 0 205.1471 16.3189 <C:\Python24\
> +2610268 0 13.1339 8.5832 +<C:\Python24\
>
> So, what command can I run instead to measure how much ripping this code out hurts performance?
Note also that when we performance tuned it, we may have been running
under lsprof, which would also penalize the extra function calls more
than real runtime would (IME).
John
=:->
-----BEGIN PGP SIGNATURE----- enigmail. mozdev. org/
7/6EACgkQJdeBCY SNAAPrBQCgjwcTX wZnqbOdgs2iCB10 qY8A sdOAxodeZcVpV9T bC
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAkx
JnYAnjIFNiwViT9
=gdz3
-----END PGP SIGNATURE-----