At least you got a response to confirm the fact that they have limited your use. The really cheap hosts often deny there is a problem, or don't answer at all.
Of course if it is their policy to severely limit your use of the machine's resources, then they need to advertise all the restrictions they have put in place before you sign up.
If they aren't letting you use 64MB for even a few seconds, then the implication is that they have crammed 100's of web sites accounts on to the same machine.
$50 x 100 users = $5000 per month per machine. Makes you think they could afford to spend the $60 on additional RAM as a one off cost.
Announcement
Collapse
No announcement yet.
PHP memory errors, not that big a site
Collapse
X
-
fwiw, this is the response I got -
While it's true that you can adjust the memory amount on the php.ini account
that does not actually increase the amount of ram your account has access to. As
this is a shared web hosting account and you share web server resources with
many other customers your account is limited to how much ram it can consume. You
will not be able to actually use 64M of the servers RAM just for your scripts.
Leave a comment:
-
Modern web servers typically have 4GB of RAM or more. So only being allowed to use 1% of the available RAM in the machine sucks.
You should ask your hosting company if they can increase the limit.
Leave a comment:
-
At any rate I would think 64M would be enough
Note that the error you get is always the same in terms of how much RAM could be allocated before failure (~38MB of RAM). So this shows the setting changes you are making, to try an increase the RAM limit, are being ignored. You never get more than 38MB.
Modern web servers typically have 4GB of RAM or more. So only being allowed to use 1% of the available RAM in the machine sucks.
You should ask your hosting company if they can increase the limit.
Leave a comment:
-
For others reading this the FAQ location is here,
http://www.wrensoft.com/zoom/support...hp_outofmemory
I've pasted the errors below, preceded by the ini_set I used:
ini_set ( "memory_limit", "512M");
Fatal error: Out of memory (allocated 38273024) (tried to allocate 257 bytes) in /usr/.../zoomsearch/search.php on line 1569
ini_set ( "memory_limit", "256M");
Fatal error: Out of memory (allocated 38273024) (tried to allocate 257 bytes) in /usr/.../zoomsearch/search.php on line 1569
ini_set ( "memory_limit", "128M");
Fatal error: Out of memory (allocated 3853516 (tried to allocate 257 bytes) in /usr/.../zoomsearch/search.php on line 1569
ini_set ( "memory_limit", "64M");
Fatal error: Out of memory (allocated 38273024) (tried to allocate 35 bytes) in /usr/.../zoomsearch/search.php on line 1572
nothing
Fatal error: Out of memory (allocated 3853516 (tried to allocate 257 bytes) in /usr/.../zoomsearch/search.php on line 1568
It might be possible that you are on (cheap) shared hosting and they have disabled your ability to use ini_set to request a higher RAM limit.
This is not a deal breaker, I just wanted to see how the php version worked and was hoping I could use the search.php script to make some modifications to the search results, (ie some event handlers to deselect check boxes when others are clicked, kinds of things I can't access in the search_template.html file). I have been using the zoom cgi with a lot of success and managed some javascript workarounds without accessing the script. Thank you for your kind attention. fwiw it was good that I boosted the RAM in php.ini, now my other pages are running faster. Thank you,
Leave a comment:
-
What is the exact error message you are seeing?
It might be possible that you are on (cheap) shared hosting and they have disabled your ability to use ini_set to request a higher RAM limit.
For others reading this the FAQ location is here,
http://www.wrensoft.com/zoom/support...hp_outofmemory
Leave a comment:
-
PHP memory errors, not that big a site
Hello,
I have searched the forums and tried the fixes suggested in the FAQ:
Q. "Fatal error: Allowed memory size of 8388608 bytes exhausted..." or similar error message
ini_set ( "memory_limit", "512M");
Leave a comment: