0.9: auto-threshold feedback

[henderea]

Please provide any feedback on the new auto-threshold feature introduced in 0.9 here. Is it making the threshold too high? Too low? Just about right? Any other feedback?

Thanks!

[ReddestDream]

It seems like it runs all the time whether I set it on high or low . . .

Also, it never frees very much much memory (only a few MB) or it shows small negative values after trimming . . .

I have 16 GB of RAM, and I manually set the memory threshold on 2 GB and the trim threshold on 4 GB.

My manual settings work fine . . .

The auto-threshold feature changes my settings over time to about 5 GB memory threshold and 7 GB trim threshold, which is WAY too high . . .

I'm using version 0.9.3 now, and the issue is still present and has been present since 0.9 . . .

[henderea]

Thanks for the feedback.

Version 0.9.3 changed the way it is done. Now instead of being completely automatic (and not working very well), it will set the thresholds to a percentage of the free memory after a full freeing ("Free memory now"). Trimming will not set the thresholds. You will most likely need to do a manual full freeing in order to get it to actually do a full freeing.

Also, it will leave the trim threshold at 0 if you have set it there manually.

Here are the numbers I use for determining the thresholds:

• Low
  • Full: 30%
  • Trim: 60%
• High
  • Full: 50%
  • Trim: 80%

Let me know how the thresholds are doing after a manual full freeing.

[ReddestDream]

OK. I'll try that . . .

Seems to be working better now, but the new thresholds (automatically set) don't appear unless the app is restarted.

My manual setting still appear to be set until the app is reset even though the app is now acting on the automatically set values . . .

New thresholds (Low):

Memory: 2962 MB

Trim: 5923 MB

Still a bit higher than my manual settings, but much better than before . . .

It would be nice if auto-threshold could somehow adapt to memory usage over time . . .

I'm using this app because I keep a lot of tabs (30+) open in Safari for long periods of time (days to weeks), and, eventually, memory leaks and usage in general build up to the point where the system automatically closes all my programs and logs me out to free memory. It would be nice if MemoryTamer could somehow preempt this process . . .