This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author swalker
Recipients swalker
Date 2009-07-28.20:19:19
SpamBayes Score 5.986737e-08
Marked as misclassified No
Message-id <1248812361.89.0.626576705519.issue6594@psf.upfronthosting.co.za>
In-reply-to
Content
The json serializer's performance (when using the C speedups) appears to
be tied to the depth of the structure being serialized on some systems.
 In particular, dict structure that are more than a few levels deep,
especially when they content mixed values (lists, strings, and other
dicts) causes severe serialization penalties (in the neighborhood of an
extra 20-30 seconds) on some systems.

On SPARC systems, this is very likely because of the recursive call
structure that the C speedups serializer uses which doesn't work well
with SPARC due to register windows.

On x86 systems, recursive call structures are cheap, so this doesn't
appear to be an issue there.

SPARC systems with higher amounts of memory bandwidth don't suffer as
badly from this (such as Niagra T1000, T2000, etc. systems), but older
UltraSparc systems are especially prone to performance issues.
History
Date User Action Args
2009-07-28 20:19:22swalkersetrecipients: + swalker
2009-07-28 20:19:21swalkersetmessageid: <1248812361.89.0.626576705519.issue6594@psf.upfronthosting.co.za>
2009-07-28 20:19:20swalkerlinkissue6594 messages
2009-07-28 20:19:19swalkercreate