About the WU names.... |
Message boards : Number crunching : About the WU names....
Author | Message |
---|---|
RobertE Send message Joined: 15 Sep 07 Posts: 1 Credit: 56,739 RAC: 0 |
What is the difference between the test3 and the HCEYZ workunits? |
TJM Project administrator Project developer Project scientist Send message Joined: 25 Aug 07 Posts: 843 Credit: 267,994,998 RAC: 0 |
None, only name template has been changed. work units are divided into 4 types, because the number of VI-VIII rotors and their locations has an effect on processing speed. I-V I-V I-V = type 0, VI-VIII I-V I-V = 0 I-V I-V VI-VIII = 1 I-V VI-VIII I-V = 2 I-V VI-VIII VI-VIII = 3 runtime taken from reference machine: 0 ~1h 7m 1 ~2h 6-10m 2 ~2h 25-35m 3 ~4h 20-30m EDIT: btw, I've just changed hcezy to hceyz in your post. M4 Project homepage M4 Project wiki |
Sou'westerly Send message Joined: 12 Sep 07 Posts: 2 Credit: 2,754 RAC: 0 |
Credits look a bit low. I'm using a standard client and only get about 2/3 of my claimed credits. Could be a few mumbles here. Dave, |
John Hunt Send message Joined: 11 Sep 07 Posts: 5 Credit: 252,476 RAC: 0 |
Credits look a bit low. I'm using a standard client and only get about 2/3 of my claimed credits. Could be a few mumbles here. Dave, The Boinc version you are using is still (sort of) experimental. Most projects still recommend Boinc 5.10.x. |
Sou'westerly Send message Joined: 12 Sep 07 Posts: 2 Credit: 2,754 RAC: 0 |
The Boinc version you are using is still (sort of) experimental. Hi John, This client isn't over claiming or inflating the benchmarks, first thing I check with a new client. You have prompted me to look a bit further though since your intels seem to be doing the Work Units in the time expected by the project but my AMD appears to be taking roughly half as long again. All the best Dave. |
Bober [B@P] Send message Joined: 2 Sep 07 Posts: 1 Credit: 273,155 RAC: 0 |
|
TJM Project administrator Project developer Project scientist Send message Joined: 25 Aug 07 Posts: 843 Credit: 267,994,998 RAC: 0 |
Someone asked me today about the WU names, I'll repost the answer here for everyone to see. For example, let's take a look at m3_rxpsb70_1: m3 - obviously it's the machine type, if this part is missing, the wu is also M3. However, M4 workunits are always marked with 'm4' (required by the server). The next 5 (here: rxpsb) letters are the indicator group, identifying the ciphertext. After the name comes the length. It is the actual length of the workunit input file, it might be full message or just it's part (most of the time the msgs are broken into two or more parts, especially if there are letters missing). The second number (here it's p1, but most of the WUs are marked with a number) is just the batch number. Each batch is different - either it is assigned to another dict (for example, usually _1, _2 and _3 are the first 3 most used sets of dictionaries), or it might be just another part of the msg. The "p1" batch in rxpsb70_p1 is a special, experimental type of workunit. It has a missing letter somewhere at the beginning, so every 30 iterations the letter is switched to a next letter from the alphabet. With just one missing letter it's not that useful but the mechanism was designed to replace and/or add a lot more eventually missing letters. M4 Project homepage M4 Project wiki |
Message boards :
Number crunching :
About the WU names....