A little add to Fred about caching:
Every time you start Genome it makes a random number to determine that path it shall choose. As I've heard it, if you stop&restart in a wu you will make a new random number the consequent analysis follows. Then done with a wu, a new number is used if the same wu is re-processed.
The next version of Genome@home shall probably move the upload/download to another thread, so the crunching isn't stopped. It will probably also enable caching of more than one wu.
As for my calculations, it seems the crunch-time isn't linear with aa-length, but it still seems the new client is faster than the old.
Every time you start Genome it makes a random number to determine that path it shall choose. As I've heard it, if you stop&restart in a wu you will make a new random number the consequent analysis follows. Then done with a wu, a new number is used if the same wu is re-processed.
The next version of Genome@home shall probably move the upload/download to another thread, so the crunching isn't stopped. It will probably also enable caching of more than one wu.
As for my calculations, it seems the crunch-time isn't linear with aa-length, but it still seems the new client is faster than the old.
Comment