Low points

[Saenger]

Update on new WUs:

Code: Select all

Version	Runtime	CPU-Time	Grant	C/h clock	C/h CPU	#WU
V2.04	 33919,35	 30145,28	 293,17	31,12	35,01	462,00
V3.00	 14052,25	 13021,14	 292,70	74,99	80,92	 10,00
V3.01	 87642,36	 80438,70	1035,53	42,54	46,34	 60,00
V3.04	183672,24	169940,70	1971,23	38,64	41,76	103,00
V3.05	   655,19	   643,18	   6,57	36,10	36,77	  1,00
V3.06	 20277,04	 18786,81	 285,35	50,66	54,68	 10,00

3.06 is giving very good credits.

[Nflight]

As with the previous poster in this topic of Low Points I see a great improvement in the points values. Thank You Very Much

[Stef42]

At this moment I get WU's with runtime <1000 sec, so quite small.

About the errors, I'm currently running 24/7 and I get around 8-10 errors a day, fairly normal to me.

[Stef42]

No work available?!

[Nflight]

With this project when the crunchers speak the admins act, and they seem to do it immediately. Therefore it is best to tell all of you that the next batch of work units will probably have checkpoints in them. This is why we don't currently have work to crunch.

I have to commend the admins for taking action so quickly. Also the fact you listen to the people crunching your data with such esteem to act upon those effects to better everyone's working relationship. I can not speak for everyone but the responses I have seen and the actions taken in a timely manner means that results will follow quickly and effectively for everyone involved.

[chill]

Sorry for the lack of work; there was a problem with the script that submits new jobs. We are actively developing and testing some new code which means that we will have some bugs. I will try to fix problems as quickly as possible.

[Mankka*]

Hi !

I did some test runns with eOn on a couple of i7's today to check out the new credits.
The average I got was around 13 credits/core/hour.
If I compare to Primaboinca which gives an average of 90 credits/core/hour on the same computers, the new credits here are faaaar from good :(

I'm not complaining, but the fact is, if you want crunchers to be interested in eOn, you have to do something about it.

Keep up the good work guys and enjoy the summer !
I hope you will be able to solve the issue =)

Mankka*

EDIT:

The first wu's went ok after that they really started to slow down (these ones are not included in the average calculations) after 2 hrs 52% done when the first
ones only took about 15-20 min to run ??? (only Collatz running on the GPU's, so nothing had changed during the test)

[chill]

The first wu's went ok after that they really started to slow down (these ones are not included in the average calculations) after 2 hrs 52% done when the first
ones only took about 15-20 min to run ??? (only Collatz running on the GPU's, so nothing had changed during the test)

Right now we are running workunits that have a wide distribution in run times. The wu names have a number prefix and those with the same prefix will have similar runtimes.

[Stef42]

A nice stream of workunits, great!

[Nflight]

Please See "Longer Work Units" post for exacting details. Seems the points values have decreased once again, 7+ hours per work unit resolves just less then 3 points per hour! That's down right awful..!

[Tex1954]

The new 3.09 eOn Client is taking a whopping long time to run on all my systems... and the points are all over the place... and the Run Time vs. CPU Time seems weird somehow...

103783550 112945479 16,695.67 16,585.23 12.76 eOn Client v3.09
103783279 112945208 15,043.16 14,587.26 24.91 eOn Client v3.09
103783223 112945152 13,782.73 13,355.73 24.13 eOn Client v3.09
103774323 112936252 7,605.32 5,590.39 69.19 eOn Client v3.09
103774908 112936837 3,360.93 1,806.18 15.24 eOn Client v3.09
103783550 112945479 16,695.67 16,585.23 12.76 eOn Client v3.09
103783549 112945478 17,039.58 16,785.03 30.72 eOn Client v3.09


3.08 ran somewhat less wildly...

3.08 gave me SOLID 0.0018 Points Per Second CPU Run Time no matter the length of the WU.
3.09 is giving 0.0011 to 0.0045 Points Per Second CPU Run Time and makes no sense.

And then I get 8 errors in a row after crunching an hour on each...

103789704 112951635 Error while computing 4,019.75 3,893.21 --- eOn Client v3.09
103789697 112951628 Error while computing 4,020.03 3,899.06 --- eOn Client v3.09
103789518 112951449 Error while computing 4,003.18 3,906.76 --- eOn Client v3.09
103789362 112951293 Error while computing 4,003.18 3,881.48 --- eOn Client v3.09
103790332 112952263 Error while computing 3,933.82 3,838.26 --- eOn Client v3.09
103790305 112952236 Error while computing 3,933.82 3,849.06 --- eOn Client v3.09
103790274 112952205 Error while computing 3,934.36 3,852.29 --- eOn Client v3.09
103790273 112952204 Error while computing 3,934.36 3,845.85 --- eOn Client v3.09

And then I get 2 errors in a row after crunching to 100% on each...!!!!

103783600 112945529 Error while computing 18,035.77 17,846.70 --- eOn Client v3.09
103783580 112945509 Error while computing 18,035.77 17,806.42 --- eOn Client v3.09

Something is wrong with this picture somehow... like the longer to run the less the points or something? Makes no sense!

I think there is something wrong with 3.09!!!!

[Jwb52z]

This is my first post joining this DC project. I'm so glad it's not just me experiencing the long long long WU times. I don't get any errors though. My longest WU is going on over 20 hours. This is crazy because I've never seen any DC project that used BOINC do this.

[chill]

This is my first post joining this DC project. I'm so glad it's not just me experiencing the long long long WU times. I don't get any errors though. My longest WU is going on over 20 hours. This is crazy because I've never seen any DC project that used BOINC do this.

The most recent batch of work that was submitted is taking longer than expected. We try not to submit work that takes quite that long.

[Jwb52z]

Just for information purposes, in case it's useful, the longest WU I have no is over 22 hours to be exact.

[modesti]

[Prepared on Fri, 29th July - waiting for registration on the forum]

Hello,

this morning I found several WUs of V3.09 on my i7 860 (Win7 64b) that were running for nearly 5 hours. The least problem is that – due to the short deadline – they were/are all in high priority.

The bigger problem I found were the granted credits.
http://eon.ices.utexas.edu/eon2/results ... =0&state=3

Code: Select all

103782879 	112944808 	29 Jul 2011 0:59:07 UTC 	29 Jul 2011 5:56:48 UTC 	Completed and validated 	17,846.34 	16,896.33 	10.17 	eOn Client v3.09
103782828 	112944757 	29 Jul 2011 0:57:59 UTC 	29 Jul 2011 6:42:03 UTC 	Completed and validated 	20,629.32 	19,779.48 	11.48 	eOn Client v3.09
103781280 	112943209 	28 Jul 2011 22:21:38 UTC 	29 Jul 2011 4:06:22 UTC 	Completed and validated 	20,322.76 	19,161.26 	6.80 	eOn Client v3.09
103781011 	112942940 	28 Jul 2011 22:27:32 UTC 	29 Jul 2011 4:22:58 UTC 	Completed and validated 	21,311.43 	20,113.44 	7.55 	eOn Client v3.09
103780733 	112942662 	28 Jul 2011 21:47:55 UTC 	29 Jul 2011 2:49:15 UTC 	Completed and validated 	18,065.38 	16,848.31 	4.36 	eOn Client v3.09
103780566 	112942495 	28 Jul 2011 21:44:37 UTC 	29 Jul 2011 4:48:49 UTC 	Completed and validated 	25,249.45 	24,074.46 	8.22 	eOn Client v3.09
103776483 	112938412 	28 Jul 2011 19:22:54 UTC 	28 Jul 2011 22:22:42 UTC 	Completed and validated 	10,713.89 	9,632.20 	25.04 	eOn Client v3.09
103776389 	112938318 	28 Jul 2011 19:18:53 UTC 	28 Jul 2011 22:28:37 UTC 	Completed and validated 	11,079.95 	9,968.34 	26.81 	eOn Client v3.09
103776127 	112938056 	28 Jul 2011 18:56:41 UTC 	28 Jul 2011 21:49:00 UTC 	Completed and validated 	10,263.77 	9,908.15 	22.45 	eOn Client v3.09
103776122 	112938051 	28 Jul 2011 18:56:41 UTC 	28 Jul 2011 21:45:44 UTC 	Completed and validated 	10,066.81 	8,940.96 	21.27 	eOn Client v3.09
103772938 	112934867 	28 Jul 2011 16:22:56 UTC 	28 Jul 2011 19:23:59 UTC 	Completed and validated 	10,786.43 	9,777.10 	23.42 	eOn Client v3.09
103772907 	112934836 	28 Jul 2011 16:17:11 UTC 	28 Jul 2011 19:20:00 UTC 	Completed and validated 	10,557.59 	9,562.10 	22.06 	eOn Client v3.09
103769507 	112931436 	28 Jul 2011 13:18:17 UTC 	28 Jul 2011 16:24:02 UTC 	Completed and validated 	3,398.22 	3,006.67 	7.36 	eOn Client v3.09
103768542 	112930471 	28 Jul 2011 12:35:45 UTC 	28 Jul 2011 16:18:18 UTC 	Completed and validated 	11,949.59 	10,887.73 	24.71 	eOn Client v3.09
103765723 	112927652 	28 Jul 2011 9:33:43 UTC 	28 Jul 2011 11:19:47 UTC 	Completed and validated 	3,191.34 	3,042.11 	9.19 	eOn Client v3.09
103765721 	112927650 	28 Jul 2011 9:33:43 UTC 	28 Jul 2011 10:43:35 UTC 	Completed and validated 	2,938.59 	2,783.03 	8.32 	eOn Client v3.09
103765695 	112927624 	28 Jul 2011 9:32:23 UTC 	28 Jul 2011 13:18:17 UTC 	Completed and validated 	9,393.52 	8,843.18 	20.91 	eOn Client v3.09
103765694 	112927623 	28 Jul 2011 9:32:23 UTC 	28 Jul 2011 12:35:45 UTC 	Completed and validated 	9,389.88 	8,950.84 	26.71 	eOn Client v3.09
103765665 	112927594 	28 Jul 2011 9:31:10 UTC 	28 Jul 2011 10:20:04 UTC 	Completed and validated 	2,918.15 	2,626.90 	8.20 	eOn Client v3.09
103765657 	112927586 	28 Jul 2011 9:31:10 UTC 	28 Jul 2011 11:50:55 UTC 	Completed and validated 	8,340.40 	7,848.19 	23.73 	eOn Client v3.09 

If you compare the last line with the first one, you get 10.855 cr/h vs. 2.167 cr/h.
Usually, I don't care very much about credits, but I won't let my computer run for as less as 2 cr/h. Even Biology projects pay better.
Maybe you could look into the matter?


added: The last WUs ran over 6.5 hours and paid about 2.26-2.27 cr/h :-/