Installation and flush freeze

[damnick]

installation and flush report the following error:

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 4980736 bytes) in /tmp/silverstripe-cache-var-www-silverstripe/cache.php on line 4

[sharvey]

How much PHP memory is allocated?

[sminnee]

It looks like 32 megs is no longer sufficient :-(

[sharvey]

Generally I've noticed this happening.

Here's a forum post with the same problems:

http://silverstripe.com/site-builders-forum/flat/53812?showPost=62999

[ischommer]

thats not a specific bug in silverstripe - i certain configurations PHP can run out of memory. there are a couple of dozen posts about this on the forum :)

[sharvey]

Well, it is a problem if we say "we support 32M PHP memory" - should we updated the server requirements wiki page? - http://doc.silverstripe.com/doku.php?id=server-requirements&s=php%20memory

[ischommer]

Sorry, was too quick to close this ticket - didn't see that this was memory usage of a plain installation.

We can't do anything about the memory requirements in the short term (e.g. rc4 release), but need to document the increased requirements. 40M or 48M seems to be a reasonable amount that many shared hosters will still support, we need to verify this is enough.

* Profile areas on a base installation:

• run installer script with db/build
• run admin interface
• run files & images with a couple of uploaded files (we're aware it fails with large number of files)

* Add note http://doc.silverstripe.com/doku.php?id=server-requirements&s=php%20memory * Modify installer to raise memory limit through ini_set if allowed, fail installation otherwise

[damnick]

I close the tickets, because I have read the forum after posting... If I have read that the problem is already know, I don't have posted the bug report.

But... I'm not a good programmer, but I think that 32/48mb of ram only for base installation is not a good thing!!!

I'm testing SS in a local server and I can assign more than 48 mb to silverstripe, but for example my provider give me only 32Mb for php.

Why silverstripe is so memory hungry?

Is a thing that can be resolved?

[sminnee]

Yes, it is definitely something that will be resolved for 2.3. However, the memory requirements are going to stand as they are for 2.2.2 because we need to get it released.

[sharvey]

Setting this to 2.2.3-feature-lock so we can resolve it then. Leaving priority as-is, as it seems important to investigate this problem.