Timeline for How to debug full RAM memory?
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 18, 2018 at 7:05 | comment | added | Mark Kaplun | .... well, maybe it will be easy to find the parts that are problematic, but since you have an already working site, what will you do if you discover than plugin X is the problem? It is not like you can replace it with Y (if something similar enough exists at all) without some manuall configuration and probably coding work | |
| Aug 18, 2018 at 7:01 | comment | added | Mark Kaplun | the cause is that you haven't followed best practice software development, and set your php memory limit too high. As you can not easily know in retrospect which part of you code is the problematic one, your only way to discover it is by setting the memory lower, and let PHP fail and generate errors when the limit is passed. This is just not going to be neither easy, nor fun. | |
| Aug 18, 2018 at 6:13 | comment | added | Peter Westerlund | Not sure I understand. Well I understand that your point is to buy more RAM. But we DON'T have much traffic. That's why it's feel strange. Why would it be bad to look up what's causing the big RAM memory loss?? Maybe we need to buy more memory anyway but. Can't really see why we just should but without find the cause first. | |
| Aug 18, 2018 at 4:31 | history | answered | Mark Kaplun | CC BY-SA 4.0 |