It seems that the [do not] "leave applications in memory when suspended" setting is not always honored. My suspicion is that some of the routes the cc may go through to suspend a task implement this setting and some do not, but I haven't identified which do or do not.

(some "routes" I can think of off the top of my head:
Suspend when user is active
Only allow work at a particular time of day
Suspend when running benchmarks (maybe this one shouldn't honor the setting, I don't know))

If anyone knows of a workaround, I'd be glad to hear it! I'm running this on a quad CPU server that is my compute server, and I can't afford to have ram wasted on four tasks when I'm running my batch reports, so otherwise I'll have to uninstall which would be too bad.

Thanks!

---

Particularly if you don't allow them to remain in memory, the client will try to wait for the application to checkpoint before suspending it and resuming another. However, in the "user active" case, it can't wait: it has to suspend it immediately. Maybe the application is left in memory in that case to avoid wasting CPU time.

---