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.
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.
- Previous 10 entries
- 1
- Page 22(current)
- 3
- Next 10 entries
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.
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 :)
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?
Also, what is debug memory measured in? Is it Bytes?
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/
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.
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.
- Previous 10 entries
- 1
- Page 22(current)
- 3
- Next 10 entries