@monkeycloud: That's a neat idea about using the Poser API (another interesting project to get into), but we're still bottle necked by the sheer size of the actual poser files. Most of mine are moderate single frame scenes in the 200's (MB).

However... having said that we could setup a low grade Poser Request Server, as it were, to handle the transfer of the save file, then automatically kick off another Cloud Cluster GPU instance once the file is uploaded using the Request Server Poser interface to post to the Cloud LAN QM and have the Cluster GPU QM pick it up for processing (and of course shut it down once done processing its queue). That would optmize the time/cost of the machines that are actually running.

It still doesn't address the data transfer issue but it's a start :)