Somewhat limiting....

>>> This project doesn't support computers of type windows_x86_64

I got the same message with linux. Likely because there are no apps for this project yet.
https://comp.ithena.net/usr/apps.php

---

Exactly right.
The app is not yet added ;)

It is all a Halloween trick ;)

How soon can we expect the treats?

This is not just a joke :)
The Haloowen date is a total coincidence.
I have been planning to add compute (CPU) tasks for a very long time.
We plan to add the first test graph application soon (depending on how fast it passes initial testing).

Getting work now, but all are ending in computational errors after about 4min 20 sec.

<core_client_version>7.16.6</core_client_version>
<![CDATA[
<message>
exceeded elapsed time limit 248.95 (1440.00G/5.78G)</message>
<stderr_txt>
07:00:22 (343108): wrapper (7.5.26014): starting
07:00:22 (343108): wrapper: running ithena_graph_v1.02_x86_64-pc-linux-gnu (--silent)

</stderr_txt>
]]>

I have corrected this bug in the next versions of the tasks.
We are waiting for confirmation...

If possible, please let me know how long the iThena GRAPH tasks currently count with you?
How much time do you have in current tasks already (in progress on client)?

I have corrected this bug in the next versions of the tasks.
We are waiting for confirmation...

All are running past the 4min 20sec mark now. Now to see if they finish and validate.

All are running past the 4min 20sec mark now. Now to see if they finish and validate.

So we wait.
If you can you report the information :)

First "Success":
https://comp.ithena.net/usr/workunit.php?wuid=5321 :)

After 2 hours and 28 minutes still exceeding the time limit on a v1.02...

<core_client_version>7.17.0</core_client_version>
<![CDATA[
<message>
exceeded elapsed time limit 8896.48 (54400.00G/6.11G)</message>
<stderr_txt>
10:56:03 (3632738): wrapper (7.5.26014): starting
10:56:03 (3632738): wrapper: running ithena_graph_v1.02_x86_64-pc-linux-gnu (--silent)

</stderr_txt>
]]>

Is there a reason you can't set it high and then reduce that figure once you've worked out how long they should actually run for ?

Agreed. It seems that these tasks have a very wide range of run times depending on the computer, and your estimate and max run time limit are too low.

Tasks running on my Xeon E5-1650 v4 are estimating run times of around 3.3 - 3.5 hours. And tasks running on my Ryzen 9 3900X are estimating run times of more than 5 hours. Both of these computers are normally a lot faster than the Xeon E3 1220 test machine mentioned in the announcement message, but are not running the .Computational tasks that fast and need to have more time allowed to finish the tasks.

Also, these tasks are actually using more than one CPU thread per task. On the E5-1650 with 6 cores/12 threads I had to reduce the number of running tasks down to 8 before the total CPU usage dropped below 100%. On the 3900X with 12 cores/24 threads, I had to drop it down to 18 running tasks to get the total CPU usage below 100%.

If the tasks were actually just using one CPU thread each, the totals would have dropped below 100% at 11 tasks on the E5-1650 and 23 tasks on the 3900X...

This might explain the higher run times than the original estimate as well. For those of us who usually run a number of tasks equal to the number of CPU threads, the tasks aren't getting the amount of CPU time that they want.

Agreed, they run longer, but still error out.

<core_client_version>7.16.6</core_client_version>
<![CDATA[
<message>
exceeded elapsed time limit 11031.19 (54400.00G/4.93G)</message>
<stderr_txt>
07:35:32 (482679): wrapper (7.5.26014): starting
07:35:32 (482679): wrapper: running ithena_graph_v1.02_x86_64-pc-linux-gnu (--silent)

</stderr_txt>
]]>

On a side note, based on the task in the link in the "First Success" post made earlier, I realize that this is still the basic testing stage, but if you want people to continue to participate in the new CPU intensive project, you need to give a LOT more than 8 credits for CPU tasks that take several hours to complete!

I've noticed problems.
I increased 10x the possible execution time.
I set it to 40 credits per WU at this moment.
There is a new specification for tasks in the new series "TESTS_1A_T..."

First "Success":
https://comp.ithena.net/usr/workunit.php?wuid=5321 :)

Cool, that one's mine. For reference, it's a real Linux machine, not a VM. It's a Haswell-class Intel i5.

I set up everything linuxy last night to automatically grab tasks here when they became available. That may lead to some problems with timeouts., since there's now multiple VMs plus host systems overcommitting cpu cores. I've paired it back a bit.

One of the systems running tasks is an *old* laptop. Really slow. We'll see how long it takes.

If I'm setting time limits on tasks, I generally look at the slowest active computer in the database, figure out how long it should take to run a task, and multiply *that* by 10. There's all sorts of reasons why tasks will run slower than 'normal',

---

Want to find one of the largest known primes? Try PrimeGrid. Or help cure disease at WCG.

I've noticed problems.
I increased 10x the possible execution time.
I set it to 40 credits per WU at this moment.
There is a new specification for tasks in the new series "TESTS_1A_T..."

Looks like my slow machine is going to need about 8 to 10 hours per task. That's a 1st gen i3 (2c/4t) laptop, with your tasks run on two threads and some heavy computational stuff (prime95-ish) on the other 2 threads.

---

Want to find one of the largest known primes? Try PrimeGrid. Or help cure disease at WCG.

On an Intel Xeon E3 1220 @ 3.10GHz processor the computation time should be ~177 minutes.

This time Xeon E3 1220 was actually on 1 core and at a time when the other 3 cores were in idle.
In fact if I had run the x4 application (all core) it could have been quite a bit slower.

hello
on one of my PCs
Intel(R) Core(TM) i7 CPU 870 @ 2.93GHz [Family 6 Model 30 Stepping 5]
(8 processors)
computer 94
I received 152 WU at the same time, is this normal?
thank you