Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:37693 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 52814 invoked from network); 17 May 2008 14:55:15 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 May 2008 14:55:15 -0000 Authentication-Results: pb1.pair.com header.from=parasane@gmail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=parasane@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.46.31 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: parasane@gmail.com X-Host-Fingerprint: 74.125.46.31 yw-out-2324.google.com Received: from [74.125.46.31] ([74.125.46.31:16633] helo=yw-out-2324.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 7F/12-33811-2D1FE284 for ; Sat, 17 May 2008 10:55:15 -0400 Received: by yw-out-2324.google.com with SMTP id 5so753664ywb.83 for ; Sat, 17 May 2008 07:55:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=1X0WP5TPy5oseCyqdxRQ5ihZ18jSIbwFuhk8e5hGJ/M=; b=Fx822NMzTqRHZwD0gRC9bavwxcpPglpIcxamHB5TMTz22vYI5RXHD6MPBBL69zLhNMFaNubQw+zMuryBDYL5Ax99hG6zTYBqUK24speb5Gs3EMI/CNq7uHbiqXSU+FcYTr6t5DNbeTO6STpWxfCElNkoPXGoYHkX8p48ehFQv/4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=bZEeM6536kGA7oKXHDefhtqqqnDHNsr/J1PDJSxTEqTtmwcTuNStrJ+qfSOoB8+H0v5Bhz062zkCDNcoVzcxINFwrYhXBTdCCzw+ANMpdhniM+nUuRDhP7I/01Hr1sq00TxHjnfukOP296YryOKO4BLqhhUSh88GsTBVTSCNLUI= Received: by 10.150.11.6 with SMTP id 6mr4655805ybk.9.1211036112227; Sat, 17 May 2008 07:55:12 -0700 (PDT) Received: by 10.150.98.14 with HTTP; Sat, 17 May 2008 07:55:12 -0700 (PDT) Message-ID: Date: Sat, 17 May 2008 10:55:12 -0400 To: "Rasmus Lerdorf" Cc: "PHP Developers Mailing List" In-Reply-To: <482E8391.9080004@lerdorf.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <482E8391.9080004@lerdorf.com> Subject: Re: [PHP-DEV] Curl POST emalloc leak? From: parasane@gmail.com ("Daniel Brown") On Sat, May 17, 2008 at 3:04 AM, Rasmus Lerdorf wrote: > > start 326616 > GET 327256 > GET 327276 > GET 327276 > GET 327276 > GET 327276 > GET 327276 > GET 327276 > GET 327276 > GET 327276 > GET 327276 > POST 327516 > POST 327588 > POST 327652 > POST 327712 > POST 327892 > POST 328064 > POST 328228 > POST 328384 > POST 328528 > POST 328628 It's not a solution, Rasmus, but here's more data, taken from 5.2.4. The results were exactly the same, in the same order, after running your code ten times. start 57140 GET 57820 GET 57820 GET 57820 GET 57820 GET 57820 GET 57820 GET 57820 GET 57820 GET 57820 GET 57820 POST 58244 POST 58492 POST 58728 POST 58948 POST 59060 POST 59164 POST 59264 POST 59360 POST 59452 POST 59452 When changing the for() loop in the curl() function to this: The results stabilize quicker: start 57688 GET 58340 GET 58340 GET 58340 GET 58340 GET 58340 GET 58340 GET 58340 GET 58340 GET 58340 GET 58340 POST 58844 POST 59088 POST 59416 POST 59692 POST 59800 POST 59904 POST 59904 POST 59904 POST 59904 POST 59904 -- Dedicated Servers - Intel 2.4GHz w/2TB bandwidth/mo. starting at just $59.99/mo. with no contract! Dedicated servers, VPS, and hosting from $2.50/mo.