Bug #77222 [Opn->Fbk]: memory_limit Greater then 64M slows down reply

From: Date: Wed, 08 Apr 2020 11:18:03 +0000
Subject: Bug #77222 [Opn->Fbk]: memory_limit Greater then 64M slows down reply
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-226480@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=77222&edit=1

 ID:                 77222
 Updated by:         cmb@php.net
 Reported by:        jpmiguel at yahoo dot com
 Summary:            memory_limit Greater then 64M slows down reply
-Status:             Open
+Status:             Feedback
 Type:               Bug
 Package:            IIS related
 Operating System:   Windows 2008 RC2
 PHP Version:        7.2.12
-Assigned To:        
+Assigned To:        cmb
 Block user comment: N
 Private report:     N

 New Comment:

Thank you for this bug report. To properly diagnose the problem, we
need a short but complete example script to be able to reproduce
this bug ourselves.

A proper reproducing script starts with <?php and ends with ?>,
is max. 10-20 lines long and does not require any external
resources such as databases, etc. If the script requires a
database to demonstrate the issue, please make sure it creates
all necessary tables, stored procedures etc.

Please avoid embedding huge scripts into the report.


Previous Comments:
------------------------------------------------------------------------
[2018-11-30 03:00:57] jpmiguel at yahoo dot com

Description:
------------
I have a server using php-cgi on a new site we are putting on production.
And it behaves very poorly with around 4 seconds before the first reply. After the php delivers the
html the page and all the scripts and images load almost instantly.

After some tweaks I realized that if I lower the memory-limit below 64M on the php.ini it behaves
much better (0.6 seconds).

But I cant keep the memory limit that low because I will get "Allowed memory size of 67108864
bytes exhausted" from time to time.

Can you please check or point me on a way to solve this?

Thanks



------------------------------------------------------------------------



--
Edit this bug report at https://bugs.php.net/bug.php?id=77222&edit=1


Thread (4 messages)

« previous php.bugs (#226480) next »