Originally Posted by
BlindFreddie
Sorry, D_A, but you misunderstood me. I didn't mean to imply that the AutoDock WUs have a problem, other than that they don't show a huge speed advantage when run under Linux.
I want to run only FAHV WUs under Linux, with other WU types under Windows, to maximise throughput of my machines.
But the Linux machines have to accept AutoDock WUs as well as FAHV ones. That's what I'd like fixed.
WCG could:
1) (easy) Divert nearly all of the faah WUs sent out, to Windows and Mac boxes, sending any needed extra FAHV ones to Linux boxes, or
2) (harder) Run the FAAH project as 2 sub-projects, letting us choose the WU types that we want. The FAAH project would have 2 selection flags on the device profile pages, 1 for AutoDock, the other for VINA.
Enabling the diversion of WUs of various types to the machines on which they run fastest would enable more efficient use of our crunching resources, and raise WCG's total throughput.
Thanks for the info that most of the programs run faster under Linux. I thought that it was the opposite, except for VINA.
ATM, I'm running all machines with Win7-x64 native, and Debian 7.2 in VMs under VMWare. I will allocate more cores to the Linux VMs and fewer to Windows.
I tried VirtualBox, but it seems rather inefficient. OTOH the overhead of WMWare seems to be negligible.
Without me having to dig for the info, does anyone know how to get the VMs to autostart at host system boot time?