On a particular hardware setup, I was able to hit about 2.25-2.75 Million per day and I was carrying about 3000-3600 validation inconclusive (pending) at the time. I took a little time off, historic heatwave, and now I'm ramping back up with the same hardware. I now have 6000 validation inconclusive (pending) and I'm getting like 1.75-1.9 million per day.

Anyone else seeing higher than normal amounts of (pendings)?

Please see the thread here: https://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=4732&postid=70953#70953

I am testing a new validator that should fix these problems. I hope to roll it out early next week.

Please see the thread here: https://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=4732&postid=70953#70953

I am testing a new validator that should fix these problems. I hope to roll it out early next week.

Hello Tom
I think it is still not fixed. After pushing my new computer (id 825437 ), 15 inconclusive for 1 valid !

Best regards

It is "fixed", but the system got another oversized WU stuck in it again. I'm hoping this was a fluke. I cleared that oversized WU out, and hopefully you should see the errors dropping again.

I still need to figure out why these things get generated in the first place.

Has the Validator got a problem, my validation pending total is going up steadily.

I see the Workunits waiting for validation on the server status page, has gone up from some 8000 to over 17000 in about 2 hours.

I see the Workunits waiting for validation on the server status page, has gone up from some 8000 to over 17000 in about 2 hours.

I wonder if AMD or Intel is testing a new cpu and using MilkyWay to do it.

Looks like the validator is stuck again for some reason, queue is steadily building up.

Looks like the validator is stuck again for some reason, queue is steadily building up.

The News section says a drive is out clogging up everything

Currently the status says Workunits waiting for validation 675900

any guesses at what number the system will starting having problems? So far I'm getting plenty of WUs to run, and the website isn't slow.

Currently the status says Workunits waiting for validation 675900

any guesses at what number the system will starting having problems? So far I'm getting plenty of WUs to run, and the website isn't slow.

https://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=4842&postid=71849#71849

Currently the status says Workunits waiting for validation 675900

any guesses at what number the system will starting having problems? So far I'm getting plenty of WUs to run, and the website isn't slow.

https://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=4842&postid=71849#71849

This is a good link explaining why the WU waiting for validation is rising for anyone still wondering why

I was more curious as to what point it all goes boom. The website is starting to lag a bit for me and the WU waiting validation is 700k+ (edit to add 772546)

Just a bit of fun as a guessing game. I'm new here, so anyone know from past experience when it is too much?
I will also send the admin (Tom?) my thoughts and wishes on a speedy arrival of the drive, and an easy adding of said drive :-)

I sure hope there isn't a point where things go boom! We should be able to store ~2 billion workunits pending validation, so in theory we will be fine for a long time.

We haven't heard back about the drive yet, but it's been sent to the manufacturer.

We have passed the 2 million mark of waiting for validation (2264700) and the system is still functioning pretty well. kudos Tom! 2 billion is a high mark, and I doubt we will reach that. Nice to know the system has capacity for that much. Thanks for the info. I'll worry less now.

2.3 mill now. It was 1.7 mill yesterday, forum is slow, not that good if you ask me.

And now I'm not getting new work: There's 0 tasks ready to send according to server status :(

Thank you to whoever (Tom?) is working on a Sunday to get the server up again. I just got some tasks (resends). The server is going to take some time until it can send enough WUs to make us all happy though.
Here are some stats on the server, so I can quantify the recovery.
Transitioner backlog (hours) 19.25
Workunits waiting for validation 2446326
Tasks in progress 1438848 (This number is surprising as I would have thought it would be lower with the pause in sending out)

Thanks again to those in on a Sunday to fix things.

Bit of strangeness on these, however.
Here's a sample WU:
https://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=386958166
Pending validation, but since initial replication is 1, there's no other work in progress to be completed to validate against, at least for now.
Am I missing something here?
I have over 900 of these pending at this point. Was wondering why my RAC landed in the dumps.

---

Bit of strangeness on these, however.
Here's a sample WU:
https://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=386958166
Pending validation, but since initial replication is 1, there's no other work in progress to be completed to validate against, at least for now.
Am I missing something here?
I have over 900 of these pending at this point. Was wondering why my RAC landed in the dumps.

They still have to be processed by the Server before any credits get awarded, they don't want any bad actors scamming the system so to be safe they scan them all.

They still have to be processed by the Server before any credits get awarded, they don't want any bad actors scamming the system so to be safe they scan them all.

I think you missed the point here. Unless I misunderstand, in addition to the basics of checking the completed workunit for proper formation and content, validation is the process of comparing the results of computation of an identical result from different computers. The presumption is that different machines with different hardware providing a comparable output is an indicator of a valid task. With only one computer doing the work, validation per that definition is not possible. With only 1 returned result, that result can never validate. If that's not how the software is currently operating, we're not doing science here.

---