Code: Select all
VER RAM usage (kb) : Notes
2.0 36,982
3.5 34,556
3.6 33,316
4.0 63,500 : swings, volatility (120k)
10 68,000 : (cont., 60k) after mem optimization 65,000
20 96,000 : 500k volatile, after mem optimization 102,000
30 107,500 : 120k volatile; increase to 116,500 at idle, 3000k volatile;
mem optimization ineffective.
40 123,000 : increase to 130,000 at idle.
66 580,000 : 100mb swings ; full installation, no add-ons
Palemoon 28: 156,000 : after mem optimization 148,500
The numbers speak for themselves. Between 3.6 and 4, RAM use doubled; then doubled again by 40, and by 66...
I looked at about:memory to get a sense of where this memory is going, and I think the culprit is the IonMonkey system. IonMonkey is a dynarec process which profiles script usage to try to figure out which scripts will benefit the user most as machine code. In theory it's a means to better performance, but in practice it just sucks up resources. Images are taking next to no memory compared to egregious Javascript buffering for rainy days that rarely arrive. In theory Mozzilla codebase is faster, but in practice you just spend more for less. And the "optimize memory" function? Totally ineffective.