Re: [VOTE] RFC: Introduce session_start() options - read_only, unsafe_lock, lazy_write and lazy_destroy
| From: | Yasuo Ohgaki | Date: | Thu, 22 Jan 2015 06:42:45 +0000 |
| Subject: | Re: [VOTE] RFC: Introduce session_start() options - read_only, unsafe_lock, lazy_write and lazy_destroy | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-80953@lists.php.net to get a copy of this message | ||
Hi all,
On Thu, Jan 22, 2015 at 2:05 PM, Yasuo Ohgaki <yohgaki@ohgaki.net> wrote:
> This patch boosts PHP application performance a lot when session data
> have not changed. It's faster than benchmark in the wiki because hashing
> has removed.
>
Since it should be faster, I tried to took some benchmarks. Then I found
extremely slow
session (files handler) performance with CLI built in web server regardless
of may patch.
The script I used is
<?php
session_start();
$_SESSION['test'] = 1234;
var_dump(session_id());
?>
Fedora 21 PHP 5.6 (RPM package)
Requests per second: 5916.41 [#/sec] (mean)
Fedora 21 Master (no debug, no zts)
Requests per second: 949.56 [#/sec] (mean)
Simple script like "echo 1234;" seems working well.
Does anyone have any insight on this?
Regards,
--
Yasuo Ohgaki
yohgaki@ohgaki.net