Bug 220821

Summary: Default PHP memory_limit should be increased on 64-bit platforms
Product: [Fedora] Fedora Reporter: Elliot Lee <sopwith>
Component: phpAssignee: Joe Orton <jorton>
Status: CLOSED RAWHIDE QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhide   
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: 5.2.0-10 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-03-12 13:16:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Elliot Lee 2006-12-27 15:21:58 UTC 
Because 64-bit pointers & longs take up more memory, larger PHP scripts will not
run successfully on 64-bit platforms with default PHP configuration, even though
the same configuration allows them to run on 32-bit platforms. This is because
the memory_limit setting in /etc/php.ini is the same on both 32-bit and 64-bit
platforms.

The memory limit on 64-bit platforms should be 1.5x to 2x the limit on 32-bit
platforms.
Comment 1 Joe Orton 2007-01-03 12:51:31 UTC 
We've had fewer reports of memory_limit issues since the default was bumped to
16M everywhere (FC6) - were you still seeing this type of problem with the 16M
default?
Comment 2 Elliot Lee 2007-01-07 16:02:45 UTC 
Yes; I had to bump the limit up to 32M to get things to work on x86_64. On i386,
16M seems to work OK, and I'm sure that limit is more than enough for most people.

The main point I was making was that if the limit is N megabytes on a 32-bit
platform, it should be N*2 megabytes on a 64-bit platform.
Comment 3 Joe Orton 2007-03-12 13:16:22 UTC 
Using the N*2 value as one-size-works-everywhere is simpler; 32M seems a
reasonable stab in the dark; upstream bumped to 128M which seems too high.  This
was done in Raw Hide, thanks for the report.