23453 Posts in 18902 Topics by 2877 members
Page: 1 2
|Go to End|
27 July 2010 at 1:37am
Thanks for that.
I'll keep looking over the info you sent but the first thing that leapt out at me was the php.ini settings for max_execution_time 600.
This by default on PHP is set to 30, I never needed to have it any bigger than 30 - but you may need this. It should kill off any processes taking time at the 30 second mark.
27 July 2010 at 2:26am
Chris - that is a fantastic observation - I think it was upped recently to allow a particularly long (but stand alone) script to run and then not lowered. It still doesn't answer why all these sapphire/main scripts are persisting and eating up memory - but is most definitely something!
18 August 2010 at 7:24am
We're seeing the same issue here, on a site upgraded from 2.3.4 to 2.3.7. Even since this has happened memory has been spiralling up until eventually Apache restarts itself. Normal memory usage on the server is 280-320MB, it'll hit 800MB or so before dying.
lsof -p xxxxx indicates its httpdocs/sapphire. Investigating presently.
27 February 2011 at 3:21am
Did anyone manage to find a solution to this?
We have a site which is using up a very high amount of bandwidth and the guy who looks after our server has said that it is /sapphire/main.php that is triggering all of the alerts his end
The site gets on average 300 views a month but has used up 2gb of bandwidth so far this month..
The site uses silverstripe version 2.4.2
Is this a known problem?
27 February 2011 at 4:18pm
edward - /sapphire/main.php is the main file behind SilverStripe, it loads everything so that may not be the bottle neck.
The site gets on average 300 views a month but has used up 2gb of bandwidth so far this month.
Bandwidth is different to how much resources the site is using. Bandwidth is normally the files you are serving, people loading your pages, pictures... that sort of thing not usually related to the core of SS. The alerts your sysadmin is likely getting from SilverStripe could be memory limit issues which is a common issue.
1 March 2011 at 1:30am
@Willr.. sorry.. thats me just rushing and not reading things properly!
I will have another search through the forum or create a new thread
Page: 1 2
|Go to Top|