An explanation of the performance between php implode/explode, serialize, json, and msgpack-PHP Tutorial-php.cn

php implode/explode, serialize, json, msgpack performance comparison

Use firstimplode, serialize, json_encode, msgpack_packCreate four text files for testing.

The creation code is as follows:

 '一二三四五六七八九十', 'content2' => '一二三四五六七八九十', 'content3' => '一二三四五六七八九十' ); echo file_put_contents('implode.txt', implode(',',$arr), true).'
'; echo file_put_contents('serialize.txt', serialize($arr), true).'
'; echo file_put_contents('json.txt', json_encode($arr), true).'
'; echo file_put_contents('msgpack.txt', msgpack_pack($arr), true); ?>

Copy after login

Generate after creation

implode.txt 92 bytes
serialize.txt 165 bytes
json.txt 223 bytes
msgpack.txt 121 bytes

##Generated string size The order is as follows implode < msgpack_pack < serialize < json_encode

If the array is simple, json_encode may be smaller than serialize

For example:

$arr = array('一','二','三','四','五','六','七','八','九','十');

Copy after login

serialize is 147 bytes

##json_encode is 91 bytes

Compare implode, serialize, json_encode, msgpack_pack performance

 '一二三四五六七八九十', 'content2' => '一二三四五六七八九十', 'content3' => '一二三四五六七八九十' ); $start = microtime(true); $i = 1000000; while($i>0){ // 分别测试运行时间及内存使用情况 $tmp = implode(',',$arr); // $tmp = serialize($arr); // $tmp = json_encode($arr); // $tmp = msgpack_pack($arr); $i--; } $end = microtime(true); echo 'run time:'.($end-$start).'s
'; echo 'memory usage:'.(memory_get_usage()/1024).'KB'; ?>

Copy after login

implode 1.3225722312927s 628.50KB serialize 2.0553789138794s 628.32KB json_encode 2.5058920383453s 628.34KB msgpack_pack 1.6431028842926s 628.24KB

Copy after login

Result: Memory usage is similar, run Timeimplode < msgpack_pack < serialize < json_encode

##Compare explode, unserialize, json_decode , msgpack_unpack performance

0){ $tmp = explode(',',$data); //$tmp = unserialize($data); //$tmp = json_decode($data, true); //$tmp = msgpack_unpack($data); $i--; } $end = microtime(true); echo 'run time:'.($end-$start).'s
'; echo 'memory usage:'.(memory_get_usage()/1024).'KB'; ?>

Copy after login

explode 1.7446749210358s 628.74KB unserialize 2.1386790275574s 628.67KB json_decode 5.2423169612885s 628.84KB msgpack_unpack 2.2290098667145s 628.63KB

Copy after login

Result: Memory usage is similar, running time
explode < serialize < msgpack_unpack < json_decodeSummary, since implode/explode is not suitable for using complex structures, serialize, json, and msgpack are commonly used.
Among the three comparisons, the optimal running speed, memory usage, and space usage are msgpack, followed by serialize, and finally json.
If conditions permit,
It is recommended to use msgpack to serialize the data
.About msgpack, you can check out the article I wrote before: "MessagePack Serialization Format"
This article discusses php implode/explode, serialize, json , msgpack to compare the performance. For more related content, please pay attention to the php Chinese website.
Related recommendations:
php str_replace Explanation of the method of replacing a specified number of times

Instructions for using header, headers_sent, headers_list, header_remove

Solution to changing the integer type of field returned by mysql through PDO to String type
The above is the detailed content of An explanation of the performance between php implode/explode, serialize, json, and msgpack. For more information, please follow other related articles on the PHP Chinese website!