If BOINC is snoozed, or projects are suspended, and the leave memory resident option is enabled, does the project resume at the point in computation where it left off, or does it resume from the point of last checkpoint for WU being resumed?

Empirical evidence suggests that suspend - leave memory resident while suspended - computation is resumed from the same state as at the point of suspend.

Yes. When Leave apps in memory is not on, the task resumes from the last checkpoint (or start if the app doesn't checkpoint).

---

I wonder what happens if the system is hibernated. Based on the rules it would appear that the system state, RAM and page-file state, is written to disk. Restarting from hibernate would seem to resume computation from the point of hibernation.

This may be useful for those crunching interminahly long WU w/out checkpoint and a power down is unavoidable.

Hibernating is, effectively, similar to turning off the power. You may lose the work if the OS doesn't allow enough time to save everything.
It's not recommended for climate models.

Can anybody tell me what happens to GPU process that is suspended - if BOINC is snoozed, project manually suspended, or scheduler begins crunching on different GPU task due to switch task config - if leave memory resident option is checked?

Clearly there are implications concerning that regarding the AGP aperature segment, TurboCache (including ATI equivalent), system video memory, and shared system memory allocations.

GPU applications are always removed from GPU RAM when suspended, but for when BOINC is running benchmarks. The "Leave applications in memory" switch doesn't have any effect on this. That one is for CPU applications using system RAM only.

(Yes, GPU applications run on the CPU as well. What little system RAM they use will be kept used when LAIM is on. But you're talking about what happens to the kernels in the videocard's memory. They get flushed.)

---

I'm unclear what you mean with

GPU applications are always removed from GPU RAM when suspended, but for when BOINC is running benchmarks. The "Leave applications in memory" switch doesn't have any effect on this. That one is for CPU applications using system RAM only.

Sounds like the app remains resident in VRAM only when BOINC runs benchmarks.

However, this nugget is buried in the cc_config.xml portion of the CUDA FAQ:

There is a problem when you have your preferences set to Leave applications in memory while suspended. Any task still in the video card's RAM will stay there until you resume BOINC. Although it will not use your GPU, the amount of memory that a Seti CUDA tasks takes up (200MB+ of the VRAM) may still have impact on your other activities.

Not meaning to trip you up, but I seen the link in your signature and checked it out. While I'd already perused that tome of knowlege, I overlooked the aforementioned citation because cc_config.xml didn't seem to be germane to my question.

EDIT: found Rich Haselgrove's response to you here:

http://einstein.phys.uwm.edu/forum_thread.php?id=8254

Succinctly: VRAM is always unloaded on suspend except for benchmarks. Ergo, the FAQ needs updating.

Not meaning to trip you up, but I seen the link in your signature and checked it out.

I can't edit the FAQs at the moment anyway, it's returning all kinds of errors. So sent word to the keeper of.. waiting for him to tell me what's wrong.

---