Is this a new message or another snippet of the old one we've had problems cracking?

Mike D

---

M4 project doesn't have work available (actually it does, but it keeps sending the same last workunits until it receives everything back), so while waiting for Stefan to switch the server to another text, I split the full message to serveral short parts and set the BOINC server to run them in parallel, each with only 3 walks through the keyspace (that's around 35k workunits).

Btw, the first batch was bugged, there were around 3-4k workunits with download errors and another 3-4k with validate errors (for all these which used any CPU time credits were granted, because the problem was caused by my mistake).

---

M4 Project homepage
M4 Project wiki

Okay, this "ovgrms" need a much longer deadline!

Or is it just me, seeing ruined schedules for the work resent of enigma?

Greetings

Orion7
seti.germany

The deadline is the same as for other workunits, could you explain what's wrong ?

---

M4 Project homepage
M4 Project wiki

Today I got lots of Wus with deadlines between 11. or 14. November 2009 to 21. November 2009.

http://www.enigmaathome.net/results.php?hostid=20026&offset=20&show_names=0&state=0

But sorry, thought this was only at ovgrms. After better investigation, I see there are several normal enigma-wus between.

Hmm strange thing too ...

Greetings

Orion7
seti.germany

I think it's just the way how BOINC works: you have a fast PC with a short turnaround time (1.1 day is a lot lower than average), so the server sends you a lot of resends, some of them with shorter deadlines.

---

M4 Project homepage
M4 Project wiki

I think to have the same problem than Orion 7 from Germany.
One of my PCs just started an estimated 27h workunit received november 10th at 15:50 and to be returned before november 13th at 09:37. That may be a little difficult to reach the deadline.

Bernard du 40 from L'Alliance Francophone

---

Feel free to abort any workunit you don't like, but I think that it is just a problem with estimated time.
I've seen the same problem on my machine, longest workunits have their estimated time at around 35-40 hours while they take 8-9h maximum.
I have no idea how it could happen, I guess I made a mistake when I calculated the fpops_est. This is quite strange however, because I followed the same exact procedure I used for all the previous workunits, that always worked (benchmarked the tasks on my own PC and compared the time to a task with known fpops_est). Anyway, I'll check everything again and eventually I'll fix the templates, it has to wait a few hours though, because I'm in the middle of upgrading/fixing the workunit generator.

---

M4 Project homepage
M4 Project wiki

My concern wasn't the duration itself, but the deadline : initially it was 66h for a 27h WU, corresponding to 10h of CPU time per day.
By lack of chance, I already had other Enigma WUs in queue, so it started 24 hours later and the required CPU time had grown to a huge 15.5h/day.
In order to reach it, I didn't switch OFF my PC during the night and it ended fine.

New Workunits seem to have turned back to normal, but I still have a 70h WU running with a 14-day deadline (i.e. only 5h of CPU time per day, that looks a little bit more reasonable). It's already at 50%, and it will probably take 60 hours to complete, not so far from the estimated duration.

Super short deadline was a bug and it's fixed now (however, there's a small number of affected workunits still available in the server queue).
Wrong time estimation is another thing, for now I have no idea why it happens. I have to take a closer look at the runtime averages and fpops count.

---

M4 Project homepage
M4 Project wiki