I've noticed that the v6 clients don't upgrade the Queue Version from 5.01 to 6.00 when you migrate the FAH client from v5 to v6.
It keeps the queue version at 5.01, but does write new pieces of data to the queue that only the v6 client does.
Only when the v6 client is started without a queue.dat present, it generates a new queue.dat with queue version 6.00.
Another thing I've noticed is that starting at FAH client v5.91 the number of SMP cores the FAH client detected at startup is written to the queue.dat (in byte 544 of each queue index), but the v6.01 clients write that same value to a different part of the queue.dat too (byte 004 of each queue index). Why is it stored twice? At first I though the first value is what the client detected, and the second value is the number of cores to actually use (in case more than 8, 16, whatever CPU cores are avaiable), but even for dual Quad systems, the value 8 is written to both places where I'd expect the value 8 in the first and 4 in the second.
Observations in the queue.dat, bug or feature?
Moderators: Site Moderators, FAHC Science Team
-
- Posts: 471
- Joined: Mon Dec 03, 2007 6:20 am
- Location: Amsterdam
- Contact: