request too recent: 49 sec Messages
log in

Advanced search

Message boards : Number crunching : request too recent: 49 sec Messages

Author Message
Profile STE\/E
Avatar
Send message
Joined: 12 Jul 09
Posts: 581
Credit: 761,710,729
RAC: 0
Message 994 - Posted: 10 Sep 2009, 4:00:57 UTC
Last modified: 10 Sep 2009, 4:01:57 UTC

Something I've noticed since the Server came back up yesterday I think is I'm getting a lot of "Message from server: Not sending work - last request too recent:" messages and the Server doesn't send any work because of it.

Usually the request from the BOINC Manager are about 60-65 seconds but the Server keeps saying it's under 60 seconds & mostly in the 48-49 second range ??? I'm getting this on all my Box's from what I can see.

Computer Host ID Project Date Message
PBT-07 64B GPU MGR PBOYZTOY7 24759 Collatz Conjecture 9/10/2009 4:59:46 AM Message from server: Not sending work - last request too recent: 7 sec
PBT-07 64B GPU MGR PBOYZTOY7 24758 Collatz Conjecture 9/10/2009 4:59:46 AM Scheduler request completed: got 0 new tasks
PBT-07 64B GPU MGR PBOYZTOY7 24757 Collatz Conjecture 9/10/2009 4:59:41 AM Requesting new tasks
PBT-07 64B GPU MGR PBOYZTOY7 24756 Collatz Conjecture 9/10/2009 4:59:41 AM Sending scheduler request: Requested by user.
PBT-07 64B GPU MGR PBOYZTOY7 24755 Collatz Conjecture 9/10/2009 4:59:36 AM Message from server: Not sending work - last request too recent: 48 sec
PBT-07 64B GPU MGR PBOYZTOY7 24754 Collatz Conjecture 9/10/2009 4:59:36 AM Scheduler request completed: got 0 new tasks
PBT-07 64B GPU MGR PBOYZTOY7 24753 Collatz Conjecture 9/10/2009 4:59:31 AM Requesting new tasks
PBT-07 64B GPU MGR PBOYZTOY7 24752 Collatz Conjecture 9/10/2009 4:59:31 AM Sending scheduler request: To fetch work.
PBT-07 64B GPU MGR PBOYZTOY7 24751 Collatz Conjecture 9/10/2009 4:58:26 AM Message from server: Not sending work - last request too recent: 47 sec
PBT-07 64B GPU MGR PBOYZTOY7 24750 Collatz Conjecture 9/10/2009 4:58:26 AM Scheduler request completed: got 0 new tasks
PBT-07 64B GPU MGR PBOYZTOY7 24749 Collatz Conjecture 9/10/2009 4:58:21 AM Reporting 1 completed tasks, requesting new tasks
PBT-07 64B GPU MGR PBOYZTOY7 24748 Collatz Conjecture 9/10/2009 4:58:21 AM Sending scheduler request: To fetch work.
PBT-07 64B GPU MGR PBOYZTOY7 24747 Collatz Conjecture 9/10/2009 4:57:37 AM Finished upload of collatz_1252515801_5198_0_0
PBT-07 64B GPU MGR PBOYZTOY7 24746 Collatz Conjecture 9/10/2009 4:57:33 AM Started upload of collatz_1252515801_5198_0_0
PBT-07 64B GPU MGR PBOYZTOY7 24745 Collatz Conjecture 9/10/2009 4:57:31 AM Starting task collatz_1252515801_5229_0 using collatz version 110
PBT-07 64B GPU MGR PBOYZTOY7 24744 Collatz Conjecture 9/10/2009 4:57:31 AM Starting collatz_1252515801_5229_0
PBT-07 64B GPU MGR PBOYZTOY7 24743 Collatz Conjecture 9/10/2009 4:57:31 AM Computation for task collatz_1252515801_5198_0 finished
PBT-07 64B GPU MGR PBOYZTOY7 24742 Collatz Conjecture 9/10/2009 4:57:16 AM Message from server: Not sending work - last request too recent: 51 sec
PBT-07 64B GPU MGR PBOYZTOY7 24741 Collatz Conjecture 9/10/2009 4:57:16 AM Scheduler request completed: got 0 new tasks
PBT-07 64B GPU MGR PBOYZTOY7 24740 Collatz Conjecture 9/10/2009 4:57:11 AM Requesting new tasks
PBT-07 64B GPU MGR PBOYZTOY7 24739 Collatz Conjecture 9/10/2009 4:57:11 AM Sending scheduler request: To fetch work.
PBT-07 64B GPU MGR PBOYZTOY7 24738 Collatz Conjecture 9/10/2009 4:56:06 AM Message from server: Not sending work - last request too recent: 47 sec
PBT-07 64B GPU MGR PBOYZTOY7 24737 Collatz Conjecture 9/10/2009 4:56:06 AM Scheduler request completed: got 0 new tasks
PBT-07 64B GPU MGR PBOYZTOY7 24736 Collatz Conjecture 9/10/2009 4:56:01 AM Reporting 1 completed tasks, requesting new tasks
PBT-07 64B GPU MGR PBOYZTOY7 24735 Collatz Conjecture 9/10/2009 4:56:01 AM Sending scheduler request: To fetch work.
PBT-07 64B GPU MGR PBOYZTOY7 24734 Collatz Conjecture 9/10/2009 4:54:57 AM Finished upload of collatz_1252515801_5197_0_0
PBT-07 64B GPU MGR PBOYZTOY7 24733 Collatz Conjecture 9/10/2009 4:54:56 AM Message from server: Not sending work - last request too recent: 57 sec
PBT-07 64B GPU MGR PBOYZTOY7 24732 Collatz Conjecture 9/10/2009 4:54:56 AM Scheduler request completed: got 0 new tasks
PBT-07 64B GPU MGR PBOYZTOY7 24731 Collatz Conjecture 9/10/2009 4:54:46 AM Requesting new tasks
PBT-07 64B GPU MGR PBOYZTOY7 24730 Collatz Conjecture 9/10/2009 4:54:46 AM Sending scheduler request: To fetch work.
PBT-07 64B GPU MGR PBOYZTOY7 24729 Collatz Conjecture 9/10/2009 4:54:45 AM Started upload of collatz_1252515801_5197_0_0
PBT-07 64B GPU MGR PBOYZTOY7 24728 Collatz Conjecture 9/10/2009 4:54:43 AM Starting task collatz_1252515801_5199_0 using collatz version 110
PBT-07 64B GPU MGR PBOYZTOY7 24727 Collatz Conjecture 9/10/2009 4:54:43 AM Starting collatz_1252515801_5199_0
PBT-07 64B GPU MGR PBOYZTOY7 24726 Collatz Conjecture 9/10/2009 4:54:43 AM Computation for task collatz_1252515801_5197_0 finished
PBT-07 64B GPU MGR PBOYZTOY7 24725 Collatz Conjecture 9/10/2009 4:53:36 AM Message from server: Not sending work - last request too recent: 49 sec
PBT-07 64B GPU MGR PBOYZTOY7 24724 Collatz Conjecture 9/10/2009 4:53:36 AM Scheduler request completed: got 0 new tasks
PBT-07 64B GPU MGR PBOYZTOY7 24723 Collatz Conjecture 9/10/2009 4:53:31 AM Requesting new tasks
PBT-07 64B GPU MGR PBOYZTOY7 24722 Collatz Conjecture 9/10/2009 4:53:31 AM Sending scheduler request: To fetch work.
PBT-07 64B GPU MGR PBOYZTOY7 24721 Collatz Conjecture 9/10/2009 4:52:26 AM Message from server: Not sending work - last request too recent: 48 sec
PBT-07 64B GPU MGR PBOYZTOY7 24720 Collatz Conjecture 9/10/2009 4:52:26 AM Scheduler request completed: got 0 new tasks
PBT-07 64B GPU MGR PBOYZTOY7 24719 Collatz Conjecture 9/10/2009 4:52:21 AM Requesting new tasks
PBT-07 64B GPU MGR PBOYZTOY7 24718 Collatz Conjecture 9/10/2009 4:52:21 AM Sending scheduler request: To fetch work.
PBT-07 64B GPU MGR PBOYZTOY7 24717 Collatz Conjecture 9/10/2009 4:51:16 AM Message from server: Not sending work - last request too recent: 49 sec
PBT-07 64B GPU MGR PBOYZTOY7 24716 Collatz Conjecture 9/10/2009 4:51:16 AM Scheduler request completed: got 0 new tasks
PBT-07 64B GPU MGR PBOYZTOY7 24715 Collatz Conjecture 9/10/2009 4:51:11 AM Requesting new tasks
PBT-07 64B GPU MGR PBOYZTOY7 24714 Collatz Conjecture 9/10/2009 4:51:11 AM Sending scheduler request: To fetch work.
PBT-07 64B GPU MGR PBOYZTOY7 24713 Collatz Conjecture 9/10/2009 4:50:06 AM Message from server: Not sending work - last request too recent: 49 sec
PBT-07 64B GPU MGR PBOYZTOY7 24712 Collatz Conjecture 9/10/2009 4:50:06 AM Scheduler request completed: got 0 new tasks
PBT-07 64B GPU MGR PBOYZTOY7 24711 Collatz Conjecture 9/10/2009 4:50:01 AM Requesting new tasks
PBT-07 64B GPU MGR PBOYZTOY7 24710 Collatz Conjecture 9/10/2009 4:50:01 AM Sending scheduler request: To fetch work.

Profile Slicker
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 11 Jun 09
Posts: 2525
Credit: 740,580,099
RAC: 2
Message 998 - Posted: 10 Sep 2009, 6:36:10 UTC - in response to Message 994.

I get the same thing on one of my boxes. Yes, the server is set to 60 seconds. That keeps ill-configured GPU setups from trashing all the WUs in the ready to send queue. The question is why does BOINC Manager try again so soon after sending work. Is it that the server isn't sending the "and don't ask again for xxx seconds" when the client asks for work the first time, or is it that the scheduler on the client is sub-par?

My guess is that it is the server. The BOINC server software was updated this past weekend (if the whole system is down because of the database, might was well take the opportunity to do other maintenance at that time rather than take SETI approach and be down one day every week, right?)

Anyway, it generates additional traffic so I'd prefer it it didn't do that, but so long as it gives out work when it should and the server can keep up, I'm not going to lose any sleep over it. It is probably something that should be posted on the BOINC message board if it hasn't already been reported though. That way they can put it on the list of user requested changes to ignore for at least a year. Well, it sure does seem that way sometimes.

Profile Sabroe_SMC
Send message
Joined: 12 Jul 09
Posts: 10
Credit: 2,068,456,111
RAC: 1,221
Message 1001 - Posted: 10 Sep 2009, 7:41:51 UTC

I have the same troubles to get work. Only if I set it to "No New Tasks" and wait more then 2 minutes my rig will get work.
I set my additional work buffer to 5 days then the server gave 60 Wu. After that the server still returns the "last request too recent: xx sec" message.

I think it is the new Server Soft. Please have a look in it.
Thanks in advance

10-Sep-2009 16:07:23 [Collatz Conjecture] Restarting task collatz_1252537923_6238_0 using collatz version 110
10-Sep-2009 16:07:23 [Collatz Conjecture] Starting collatz_1252537923_6239_0
10-Sep-2009 16:07:23 [Collatz Conjecture] Starting task collatz_1252537923_6239_0 using collatz version 110
10-Sep-2009 16:07:24 [Collatz Conjecture] Finished upload of collatz_1252537923_6237_0_0
10-Sep-2009 16:08:04 [Collatz Conjecture] Sending scheduler request: To report completed tasks.
10-Sep-2009 16:08:04 [Collatz Conjecture] Reporting 1 completed tasks, requesting new tasks for CPU and GPU
10-Sep-2009 16:08:09 [Collatz Conjecture] Scheduler request completed: got 0 new tasks
10-Sep-2009 16:08:09 [Collatz Conjecture] Message from server: Not sending work - last request too recent: 48 sec
10-Sep-2009 16:09:14 [Collatz Conjecture] Sending scheduler request: To fetch work.
10-Sep-2009 16:09:14 [Collatz Conjecture] Requesting new tasks for CPU and GPU
10-Sep-2009 16:09:19 [Collatz Conjecture] Scheduler request completed: got 0 new tasks
10-Sep-2009 16:09:19 [Collatz Conjecture] Message from server: Not sending work - last request too recent: 48 sec
10-Sep-2009 16:10:04 [Collatz Conjecture] work fetch suspended by user
10-Sep-2009 16:10:06 [Collatz Conjecture] work fetch resumed by user
10-Sep-2009 16:10:07 [Collatz Conjecture] suspended by user
10-Sep-2009 16:10:08 [Collatz Conjecture] resumed by user
10-Sep-2009 16:10:08 [Collatz Conjecture] Restarting task collatz_1252537923_6238_0 using collatz version 110
10-Sep-2009 16:10:08 [Collatz Conjecture] Restarting task collatz_1252537923_6239_0 using collatz version 110
10-Sep-2009 16:10:09 [Collatz Conjecture] work fetch suspended by user
10-Sep-2009 16:12:09 [Collatz Conjecture] work fetch resumed by user
10-Sep-2009 16:12:11 [Collatz Conjecture] Sending scheduler request: To fetch work.
10-Sep-2009 16:12:11 [Collatz Conjecture] Requesting new tasks for GPU
10-Sep-2009 16:12:16 [Collatz Conjecture] Scheduler request completed: got 3 new tasks
10-Sep-2009 16:12:18 [Collatz Conjecture] Started download of collatz_1252537923_6771
10-Sep-2009 16:12:18 [Collatz Conjecture] Started download of collatz_1252537923_6773
10-Sep-2009 16:12:18 [Collatz Conjecture] Started download of collatz_1252537923_6698
10-Sep-2009 16:12:20 [Collatz Conjecture] Finished download of collatz_1252537923_6771
10-Sep-2009 16:12:20 [Collatz Conjecture] Finished download of collatz_1252537923_6773
10-Sep-2009 16:12:20 [Collatz Conjecture] Finished download of collatz_1252537923_6698
10-Sep-2009 16:13:22 [Collatz Conjecture] Sending scheduler request: To fetch work.
10-Sep-2009 16:13:22 [Collatz Conjecture] Requesting new tasks for GPU
10-Sep-2009 16:13:22 [Collatz Conjecture] work fetch suspended by user
10-Sep-2009 16:13:27 [Collatz Conjecture] Scheduler request completed: got 0 new tasks
10-Sep-2009 16:13:27 [Collatz Conjecture] Message from server: Not sending work - last request too recent: 49 sec
10-Sep-2009 16:14:25 [Collatz Conjecture] work fetch resumed by user
10-Sep-2009 16:14:33 [Collatz Conjecture] Sending scheduler request: To fetch work.
10-Sep-2009 16:14:33 [Collatz Conjecture] Requesting new tasks for GPU
10-Sep-2009 16:14:38 [Collatz Conjecture] Scheduler request completed: got 0 new tasks
10-Sep-2009 16:14:38 [Collatz Conjecture] Message from server: Not sending work - last request too recent: 50 sec
10-Sep-2009 16:14:45 [Collatz Conjecture] work fetch suspended by user
10-Sep-2009 16:18:19 [Collatz Conjecture] Computation for task collatz_1252537923_6238_0 finished
10-Sep-2009 16:18:19 [Collatz Conjecture] Restarting task collatz_1252537923_6152_1 using collatz version 110
10-Sep-2009 16:18:21 [Collatz Conjecture] Started upload of collatz_1252537923_6238_0_0
10-Sep-2009 16:18:22 [Collatz Conjecture] Finished upload of collatz_1252537923_6238_0_0
10-Sep-2009 16:18:26 [Collatz Conjecture] Sending scheduler request: To report completed tasks.
10-Sep-2009 16:18:26 [Collatz Conjecture] Reporting 1 completed tasks, not requesting new tasks
10-Sep-2009 16:18:36 [Collatz Conjecture] Scheduler request completed
10-Sep-2009 16:20:08 [Collatz Conjecture] work fetch resumed by user
10-Sep-2009 16:20:11 [Collatz Conjecture] Sending scheduler request: To fetch work.
10-Sep-2009 16:20:11 [Collatz Conjecture] Requesting new tasks for CPU and GPU
10-Sep-2009 16:20:16 [Collatz Conjecture] Scheduler request completed: got 7 new tasks
10-Sep-2009 16:20:18 [Collatz Conjecture] Started download of collatz_1252537923_6950
10-Sep-2009 16:20:18 [Collatz Conjecture] Started download of collatz_1252537923_6966
10-Sep-2009 16:20:18 [Collatz Conjecture] Started download of collatz_1252537923_6932
10-Sep-2009 16:20:18 [Collatz Conjecture] Started download of collatz_1252537923_6967
10-Sep-2009 16:20:18 [Collatz Conjecture] Started download of collatz_1252537923_6951
10-Sep-2009 16:20:18 [Collatz Conjecture] Started download of collatz_1252537923_6866
10-Sep-2009 16:20:18 [Collatz Conjecture] Started download of collatz_1252537923_6952
10-Sep-2009 16:20:20 [Collatz Conjecture] Finished download of collatz_1252537923_6950
10-Sep-2009 16:20:20 [Collatz Conjecture] Finished download of collatz_1252537923_6966
10-Sep-2009 16:20:20 [Collatz Conjecture] Finished download of collatz_1252537923_6932
10-Sep-2009 16:20:20 [Collatz Conjecture] Finished download of collatz_1252537923_6967
10-Sep-2009 16:20:20 [Collatz Conjecture] Finished download of collatz_1252537923_6951
10-Sep-2009 16:20:20 [Collatz Conjecture] Finished download of collatz_1252537923_6866
10-Sep-2009 16:20:20 [Collatz Conjecture] Finished download of collatz_1252537923_6952
10-Sep-2009 16:20:38 [Collatz Conjecture] task collatz_1252537923_6966_0 aborted by user
10-Sep-2009 16:20:39 [Collatz Conjecture] task collatz_1252537923_6932_1 aborted by user
10-Sep-2009 16:20:39 [Collatz Conjecture] task collatz_1252537923_6967_0 aborted by user
10-Sep-2009 16:20:39 [Collatz Conjecture] task collatz_1252537923_6951_1 aborted by user
10-Sep-2009 16:20:39 [Collatz Conjecture] task collatz_1252537923_6866_1 aborted by user
10-Sep-2009 16:20:39 [Collatz Conjecture] task collatz_1252537923_6952_0 aborted by user
10-Sep-2009 16:20:53 [Collatz Conjecture] work fetch suspended by user
10-Sep-2009 16:21:17 [Collatz Conjecture] Sending scheduler request: To report completed tasks.
10-Sep-2009 16:21:17 [Collatz Conjecture] Reporting 6 completed tasks, not requesting new tasks

____________
Should we shag now, or shag later?

Profile mia7077
Avatar
Send message
Joined: 19 Jul 09
Posts: 11
Credit: 142,682,390
RAC: 0
Message 1002 - Posted: 10 Sep 2009, 8:08:13 UTC

I don´t think, that is a BOINC problem, because if you look on this you can see, that the time stamps from the collatz server is wrong. I use only one GPU,
need circa 38min for one task, bat following the list it dured only ca 30min.
Additional is the reporting time wrong. the last result was reporte 14.00 UTC.

mia 7077

1134642 509355 7 Sep 2009 11:21:59 UTC 10 Sep 2009 7:38:42 UTC Completed and validated 2,259.63 83.34 0.49 166.80
1133148 508641 7 Sep 2009 10:40:34 UTC 10 Sep 2009 7:12:29 UTC Completed and validated 2,291.12 81.42 0.47 157.36
1132199 171658 7 Sep 2009 9:59:54 UTC 10 Sep 2009 6:45:55 UTC Completed and validated 2,460.58 82.74 0.48 149.79
1130958 507677 7 Sep 2009 9:14:32 UTC 10 Sep 2009 6:17:19 UTC Completed and validated 2,040.85 82.74 0.48 162.63
1129798 507117 7 Sep 2009 8:35:50 UTC 10 Sep 2009 5:53:47 UTC Completed and validated 2,628.93 83.41 0.49 164.72
1129557 507009 7 Sep 2009 8:16:17 UTC 10 Sep 2009 5:23:18 UTC Completed and validated 2,511.49 82.85 0.48 164.77
1128599 506593 7 Sep 2009 7:38:49 UTC 10 Sep 2009 4:53:55 UTC Completed and validated 2,268.25 83.13 0.49 152.25
1127545 506128 7 Sep 2009 6:57:58 UTC 10 Sep 2009 4:27:29 UTC Completed and validated 2,303.72 83.52 0.49 154.43
1126455 505731 7 Sep 2009 6:22:22 UTC 10 Sep 2009 4:00:45 UTC Completed, waiting for validation 2,219.88 83.12 0.48 pending
1125384 497032 7 Sep 2009 5:42:47 UTC 10 Sep 2009 3:34:59 UTC Completed and validated 2,276.57 81.99 0.48 164.01
1124724 504956 7 Sep 2009 5:03:14 UTC 10 Sep 2009 3:08:32 UTC Completed and validated 2,208.18 82.15 0.48 152.49
1123889 504577 7 Sep 2009 4:28:09 UTC 10 Sep 2009 2:42:18 UTC Completed and validated 2,254.16 82.40 0.48 150.85
1123119 504226 7 Sep 2009 3:51:43 UTC 10 Sep 2009 2:16:51 UTC Completed and validated 2,030.43 82.07 0.48 149.87
1122504 503931 7 Sep 2009 3:42:12 UTC 10 Sep 2009 1:54:04 UTC Completed and validated 1,965.18 82.46 0.48 147.17
1121714 503580 7 Sep 2009 2:39:40 UTC 10 Sep 2009 1:29:59 UTC Completed and validated 2,152.60 82.52 0.48 164.74
1121162 503374 7 Sep 2009 2:06:25 UTC 10 Sep 2009 1:05:05 UTC Completed and validated 2,561.02 82.77 0.48 163.17
1120217 502911 7 Sep 2009 1:27:40 UTC 10 Sep 2009 0:35:35 UTC Completed and validated 2,133.66 84.12 0.49 154.49

____________

Kimegi Tepeex
Send message
Joined: 30 Jul 09
Posts: 1
Credit: 9,982,158
RAC: 0
Message 1004 - Posted: 10 Sep 2009, 11:03:06 UTC - in response to Message 1002.
Last modified: 10 Sep 2009, 11:06:42 UTC

I don´t think, that is a BOINC problem, because if you look on this you can see, that the time stamps from the collatz server is wrong.
...
mia 7077
...

I second you !
The server clock seems to be lazy today : all timestamps reported are many hours backwards, and the difference increases as the time goes...

[edit] This message was posted at about 19:14 UTC, and edited at 19:19 UTC [/edit]
____________

Profile Bowmore
Avatar
Send message
Joined: 3 Aug 09
Posts: 18
Credit: 501,520,052
RAC: 8,581,130
Message 1005 - Posted: 10 Sep 2009, 23:18:19 UTC - in response to Message 1004.

Last night I did a reinstall of XP x64 and afterwards I attached and began cranking ... at least I thought I did. On the initial attachment it only downloaded 1 wu and immediately began doing the GPU thing. Over an hour later I returned and the cache was empty. The message log had been sitting there for all that time doing the "too soon" dance. I did NNW for a couple minutes and then things took off correctly.
____________

Pwrguru
Send message
Joined: 4 Aug 09
Posts: 4
Credit: 159,336,713
RAC: 0
Message 1006 - Posted: 11 Sep 2009, 0:07:30 UTC

I am having the same "too resent" problem but I am also unable to download more then 30 work units now.... Before the crash i was able to get 60 work units (dual core) per computer....

Profile Edboard
Send message
Joined: 12 Jul 09
Posts: 9
Credit: 97,003,539
RAC: 0
Message 1009 - Posted: 11 Sep 2009, 6:32:07 UTC - in response to Message 1006.
Last modified: 11 Sep 2009, 6:33:40 UTC

···but I am also unable to download more then 30 work units now.... Before the crash i was able to get 60 work units (dual core) per computer....


It's curious, now in a PC with a quad CPU and two GPUs (GTX295) I get 180 WUs (before I was able to get 120). It seems the limit of 30 WUs per core takes into account the GPUs too (4 + 2).

I'm using BOINC 6.6.20 (32 bits)

Profile Logan
Avatar
Send message
Joined: 2 Jul 09
Posts: 124
Credit: 37,455,338
RAC: 0
Message 1010 - Posted: 11 Sep 2009, 6:57:06 UTC - in response to Message 1009.
Last modified: 11 Sep 2009, 7:00:55 UTC

···but I am also unable to download more then 30 work units now.... Before the crash i was able to get 60 work units (dual core) per computer....


It's curious, now in a PC with a quad CPU and two GPUs (GTX295) I get 180 WUs (before I was able to get 120). It seems the limit of 30 WUs per core takes into account the GPUs too (4 + 2).

I'm using BOINC 6.6.20 (32 bits)


Yes... I get 150 in a Q6600 (XP32) with a GTX260 ((4+1)*30). I don't have any complain about that...:D
____________
Logan.

BOINC FAQ Service (Ahora, también disponible en Español/Now available in Spanish)

Profile STE\/E
Avatar
Send message
Joined: 12 Jul 09
Posts: 581
Credit: 761,710,729
RAC: 0
Message 1013 - Posted: 11 Sep 2009, 7:37:57 UTC - in response to Message 1010.

···but I am also unable to download more then 30 work units now.... Before the crash i was able to get 60 work units (dual core) per computer....


It's curious, now in a PC with a quad CPU and two GPUs (GTX295) I get 180 WUs (before I was able to get 120). It seems the limit of 30 WUs per core takes into account the GPUs too (4 + 2).

I'm using BOINC 6.6.20 (32 bits)


Yes... I get 150 in a Q6600 (XP32) with a GTX260 ((4+1)*30). I don't have any complain about that...:D


Me neither, lets you have a few more to tide you over for when the Server does it own thing ... :)

frankhagen
Send message
Joined: 12 Jul 09
Posts: 188
Credit: 14,209,854
RAC: 1,306
Message 1019 - Posted: 11 Sep 2009, 10:33:38 UTC - in response to Message 994.

server's clock is limping - status shows 11 Sep 2009 10:31:53 UTC but it's actually 16:45 UTC..
____________

Profile Slicker
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 11 Jun 09
Posts: 2525
Credit: 740,580,099
RAC: 2
Message 1030 - Posted: 12 Sep 2009, 14:45:21 UTC

The server date/time problem should be fixed now.

Pwrguru
Send message
Joined: 4 Aug 09
Posts: 4
Credit: 159,336,713
RAC: 0
Message 1044 - Posted: 14 Sep 2009, 6:12:55 UTC - in response to Message 1009.

···but I am also unable to download more then 30 work units now.... Before the crash i was able to get 60 work units (dual core) per computer....


It's curious, now in a PC with a quad CPU and two GPUs (GTX295) I get 180 WUs (before I was able to get 120). It seems the limit of 30 WUs per core takes into account the GPUs too (4 + 2).

I'm using BOINC 6.6.20 (32 bits)
I am still trying to figure out why I am only getting 30 work units now after the crash.... Can the limit be raised on GPU work because some of my machines don't have a connection and only get uploaded every 12 hours ??

Profile Slicker
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 11 Jun 09
Posts: 2525
Credit: 740,580,099
RAC: 2
Message 1047 - Posted: 14 Sep 2009, 13:40:08 UTC - in response to Message 1044.

···but I am also unable to download more then 30 work units now.... Before the crash i was able to get 60 work units (dual core) per computer....


It's curious, now in a PC with a quad CPU and two GPUs (GTX295) I get 180 WUs (before I was able to get 120). It seems the limit of 30 WUs per core takes into account the GPUs too (4 + 2).

I'm using BOINC 6.6.20 (32 bits)
I am still trying to figure out why I am only getting 30 work units now after the crash.... Can the limit be raised on GPU work because some of my machines don't have a connection and only get uploaded every 12 hours ??


That's what I get for upgrading the server! The previous version would give 30 per core and 30 per GPU. The current version broke that and the ATI changes don't work either. I have increased the gpu in progress until such time as the berkeley boyz get the scheduler code working properly.

Pwrguru
Send message
Joined: 4 Aug 09
Posts: 4
Credit: 159,336,713
RAC: 0
Message 1055 - Posted: 14 Sep 2009, 16:56:03 UTC

Thank you ......


Post to thread

Message boards : Number crunching : request too recent: 49 sec Messages


Main page · Your account · Message boards


Copyright © 2018 Jon Sonntag; All rights reserved.