Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We've moved the forum!

Please use forum.silverstripe.org for any new questions (announcement).
The forum archive will stick around, but will be read only.

You can also use our Slack channel or StackOverflow to ask for help.
Check out our community overview for more options to contribute.

Hosting Requirements /

What you need to consider when choosing a hosting provider and plan.

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo, swaiba

Out of Memory on DreamHost PS w/ high limits


Go to End


2 Posts   2651 Views

Avatar
ylluminate

Community Member, 24 Posts

6 February 2010 at 4:44am

I am running a number of SS instances on a DreamHost PS without seemingly a hitch... However, I'm seeing very large RAM utilization compared to other CMS platforms at the moment. This is actually causing something very serious to happen that halts the entire server by running it out of memory and I'm actually very generous in my memory allowances and hosting.

It appears that it is one particular instance of SS that is allowing a lot of stuck scripts to spin on forever. I need to research this quite a bit more and get to the bottom of what is going on.

Any suggestions as to how to isolate this issue out? FastCGI just keeps spawning other procs to handle the load while these others just stagnate.

Avatar
Willr

Forum Moderator, 5523 Posts

6 February 2010 at 10:43pm

Have you got any custom code that could be causing any issues? Any large queries / file read/write versions? You should be able to run SS without any issues on DreamHost. (I had the non PS version for a couple years and sure it wasn't going to set any speed records but it was able to handle all the sites I threw at it).

You might want to make sure you are writing to a temp folder by manually creating a silverstripe-cache/ folder in your ss directory and giving apache read/write access and making sure that the manifest is being generated (and therefore cached rather then relooked up every time).