Re: Re: [RFC] [DISCUSSION] pecl_http
| From: | Stanislav Malyshev | Date: | Thu, 05 Feb 2015 20:28:26 +0000 |
| Subject: | Re: Re: [RFC] [DISCUSSION] pecl_http | ||
| References: | 1 2 3 4 5 6 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-81962@lists.php.net to get a copy of this message | ||
Hi!
> Does the following kcachegrind screenshot give an idea (I used a minimum
> node cost of 10% to simplify the graph)?
>
> Left is raphf enabled (24M Ir) and on the right raphf disabled (35M Ir):
> http://dev.iworks.at/ext-http/raphf.png
>
> Have a look on the top-most far-right highlighted block, which is solely
> devoted to tearing up curl instances when raphf is disabled.
I still don't understand why the comparison is made against worst
possible implementation (going through all connection cycle every time)
as opposed to logical implementation of HTTP connection object
supporting keepalive.
--
Stas Malyshev
smalyshev@gmail.com
