Comments on: serialize() vs. var_export() vs. json_encode() Part 2 http://www.phpdevblog.net/2009/11/serialize-vs-var-export-vs-json-encode-part-2.html serialize() vs. var_export() vs. json_encode() Part 2 Comment Feed de Mon, 06 Sep 2010 07:06:25 +0000 mcw[blog] 'Ruby' Alpha 3 Comment #1 by: Jakob Ketterl http://www.phpdevblog.net/2009/11/serialize-vs-var-export-vs-json-encode-part-2.html#comment7396 http://www.phpdevblog.net/2009/11/serialize-vs-var-export-vs-json-encode-part-2.html#comment7396 Jakob Ketterl Wed, 18 Nov 2009 10:33:45 +0000 Comment #2 by: Jaimie Sirovich http://www.phpdevblog.net/2009/11/serialize-vs-var-export-vs-json-encode-part-2.html#comment7488 http://www.phpdevblog.net/2009/11/serialize-vs-var-export-vs-json-encode-part-2.html#comment7488 Jaimie Sirovich Fri, 20 Nov 2009 21:28:05 +0000
Unserialize seems to shine on recursive data. JSON decode does a lot worse. And for various reasons (both space and time?), the eval method does the worst.

If you're dealing with read-biased data that's recursive, serialize is best … I think. But YMMV. Test it. ]]>