--- JSON-XS/XS.pm	2007/03/23 18:33:50	1.12
+++ JSON-XS/XS.pm	2007/03/23 18:37:30	1.13
@@ -509,10 +509,11 @@
 in the JSON::XS distribution, to make it easy to compare on your own
 system.
 
-First is a comparison between various modules using a very simple JSON
-string, showing the number of encodes/decodes per second (JSON::XS is
-the functional interface, while JSON::XS/2 is the OO interface with
-pretty-printing and hashkey sorting enabled).
+First comes a comparison between various modules using a very short JSON
+string (83 bytes), showing the number of encodes/decodes per second
+(JSON::XS is the functional interface, while JSON::XS/2 is the OO
+interface with pretty-printing and hashkey sorting enabled). Higher is
+better:
 
    module     |     encode |     decode |
    -----------|------------|------------|
@@ -527,7 +528,7 @@
 That is, JSON::XS is 6 times faster than than JSON::DWIW and about 80
 times faster than JSON, even with pretty-printing and key sorting.
 
-Using a longer test string (roughly 8KB, generated from Yahoo! Locals
+Using a longer test string (roughly 18KB, generated from Yahoo! Locals
 search API (http://nanoref.com/yahooapis/mgPdGg):
 
    module     |     encode |     decode |
@@ -543,6 +544,12 @@
 Again, JSON::XS leads by far in the encoding case, while still beating
 every other module in the decoding case.
 
+On large strings containing lots of unicode characters, some modules
+(such as JSON::PC) decode faster than JSON::XS, but the result will be
+broken due to missing unicode handling. Others refuse to decode or encode
+properly, so it was impossible to prepare a fair comparison table for that
+case.
+
 =head1 RESOURCE LIMITS
 
 JSON::XS does not impose any limits on the size of JSON texts or Perl