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.

General Questions /

General questions about getting started with SilverStripe that don't fit in any of the categories above.

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

Tracking memory issues


Reply


17 Posts   2560 Views

Avatar
dalesaurus

Community Member, 283 Posts

26 September 2009 at 6:13pm

You both motivated me to hammer out my notes into the Wiki. I hope this is helpful, I dug out all the URL variables in the 2.3.3 codebase.

http://doc.silverstripe.com/doku.php?id=urlvariabletools

Avatar
banal

Community Member, 901 Posts

26 September 2009 at 7:43pm

That's great! A very handy list, thanks a lot.
I have to admit, as of now I didn't know quite a lot of these tools/methods. Bookmarked.

Avatar
Mo

Community Member, 510 Posts

26 September 2009 at 10:19pm

OH MY GOD!! That is so useful I don't think there is a word to accurately describe it! :)

That page has gone straight into my Silverstripe Delicious Tags!

Cheers :)

Avatar
Mo

Community Member, 510 Posts

29 September 2009 at 2:20am

Right, this server keeps crashing, I am not entirely certain it is SS to blame.

Luckily I had top running over SSH when it crashed, at the time of the crash there were 30 apache2 processes running, each using 5% of CPU.

Is this normal? I thought apache ran in one process for all requests?

Any Ideas?

Avatar
Mo

Community Member, 510 Posts

29 September 2009 at 4:41am

Also, what is debug memory measured in? Is it Bytes?

Avatar
dalesaurus

Community Member, 283 Posts

29 September 2009 at 4:55am

Bytes - http://us3.php.net/manual/en/function.memory-get-usage.php

This is certainly not normal and sounds like a server issue. Time to get in the logs and make friends at http://stackoverflow.com/

Avatar
Mo

Community Member, 510 Posts

29 September 2009 at 6:00am

Right, I have kind of worked this out.

It appears to be the blog module. It is using a massive amount of memory!

Currently, debug_memory tells me it is using 540,658,016 bytes of memory!!

What the hell is going on? I dont get it :s.

Avatar
dalesaurus

Community Member, 283 Posts

29 September 2009 at 6:26am

If you have it narrowed down to a specific module, perhaps its time to start a new discussion in the Modules forum to get more specialized feedback.

But you are not crazy, it shouldn't be doing this. Many folks have this up and running without similar issues.