robertmiles hat geschrieben:Progress rate suggests that it will run for about 150 days total.robertmiles hat geschrieben:I have a task with an estimated remaining time over 90 days, months beyond the deadline.
http://www.rnaworld.de/rnaworld/result. ... d=14953356
Size of the *.vdi file may be a problem for users running on an SSD drive.
Having only one *.vdi file (which appears to be the checkpoint file) could make the task fail if some interruption occurs while the next checkpoint is being written. Most BOINC projects keep two checkpoint files, so that their applications can still resume if writing the latest checkpoint file was interrupted and therefore incomplete.
Installing the latest Windows 10 update (Creator's Edition) interferes with reading the *.vdi file, since Windows 10 then claims that no application is listed as able to open *.vdi files. Workaround - tell VirtualBox to ignore this problem when resuming from a checkpoint.
Progress rate, and estimation of completion, are completely useless for these tasks. The only way to even remotely estimate how long they'll take to complete, is to compare against a wingman's completion time and account for difference is processor speeds/capabilities... and even then, you don't know if they were hyperthreading or not. Rough estimates of task completion times, based on my EXPERIENCE, are: 150-300 days on a fast processor, 250-550 days on a slow processor.
A checkpoint consists of both a .vdi file (which may be tiny) and a .sav file (which is huge). I also find it a bit strange that BOINC's implementation of the VBoxWrapper, only keeps 1 checkpoint for these tasks... but I also understand it. If each checkpoint consumes 700 MB of disk space, then (to some degree) it makes sense to keep 1 checkpoint and not 2.
Windows 10 Creator's Update doesn't interfere with anything, from my testing... except that it requires certain minimum versions of VirtualBox, that's all. In fact, why are you even trying to use VirtualBox Manager while a BOINC task is trying to complete? THAT can easily disturb the BOINC task (the VM can get locked, and VBoxWrapper might freak out). I'd use extreme caution before using VirtualBox Manager, for anything, while BOINC is processing VM tasks.