AQUA: Mass testing of the ROQS application will begin

[trigggl]

On a 64-bit dual core linux, it's taking hours (as in, more than 6) and giving me a measly 600. Let me know when they decide to give credit for these things.

[Mike029]

I'm noticing that my quad core is jiddery when running this aqua. In the settings I have it set to use 100% of the processors and 80% of cpu like always now the mouse get stuck and takes a sec to move. For the gpu, I'm running collatz which should not be an issue. Anyone have any ideas?

[Fogle]

Arugh, I've been running a Aqua WU now for 22 hours and it's only 51% done. I hate to abourt and lose 22 hours of crunching, but I don't know if it will ever finish. What should I do?

[Maxwell]

Arugh, I've been running a Aqua WU now for 22 hours and it's only 51% done. I hate to abourt and lose 22 hours of crunching, but I don't know if it will ever finish. What should I do?

Let it keep running. Aqua WUs take a notoriously long time. And you've be well compensated. Don't panic.

[Fogle]

Well I got a computational error after 23 hours, I would advise our team to stay away till this get to be more stable. I lost a lot of production on this project.

[dan]

I have 28 hours with 6 threads now and it's only 1.14% done. My other box is at 5% and 35 hours of processing.

[JerWA]

% done and ETA are irrelevant to the work it's doing, it's a wrapper app so BOINC has no idea.

As for the errors check your logs and see if you're hitting the disk usage issue. Then go tell AQUA about it, so they can actually fix it.

I'm still not sure what I did differently as I've not dropped a ROQS unit since early last month, and that's the only one ever (and was unrelated to the current errors it seems).

Edit: Out of curiosity are you guys time sharing AQUA and other apps? Pausing a lot? Exiting BOINC? Restarting? etc?

The two machines I have running this full time do not time share (due to scheduler problems with multi-core apps), never pause, reboot, etc or at least very very rarely.