"memory priority"

Sorry; I'm not a Windows person, which is why I was able to guess wrong about the meaning of the summary information. I know a lot about virtual memory from my experience with UNIX kernels. (Poser is a hobby; I'm a UNIX system software developer in "real life".) The performance of Poser 5 has been a subject of several discussions recently here on Renderosity, though, and several people have claimed success with "increasing the memory priority". So I just repeated that. If that's wrong, I could apologize for passing it on without caveats, but there's not much point in that.

Perhaps those people were misinterpreting the significance of raising the "priority" (general purpose) of the Poser task. On the other hand, it's equally possible that Windows does give higher "memory priority" to tasks with generally higher priority. It'd make some sense, since "raising priority" is something one generally does for realtime applications, where response latency is critical. In conjunction with that, on UNIX, one typically "locks" the application into the working set (and the working set into physical memory). "Memory priority" would actually be a pretty good way to approximate some of that with less system impact.

In any case; as I said, it's worth a try.