Hmm. Looking at a console as the client works, it looks like it sends each result straight after the work unit finishes, and immediately replenishes the cache. So it keeps a constantly full cache, rather than running it dry and then filling it up again.

It's no trouble though, just something I need to bear in mind. Crunch on.