1)
Message boards :
Number crunching :
Credit lowering
(Message 30650)
Posted 13 Sep 2009 by Copycat-Digital for WCG* Post: If cobblestones are flawed then what is the use of milestones? |
2)
Message boards :
Number crunching :
Small WUs is doing it again!
(Message 29116)
Posted 9 Aug 2009 by Copycat-Digital for WCG* Post: The current small WUs (ps_82test) are causing the WU shortage because it is increasing the network traffic. This happened not so long ago (MW WUs was as scarce as rocking horse poo) and was corrected by increasing the WU length because the ATI app. crunch a WU in no time. Experience normally prevents someone not to make the same mistake again! |
3)
Message boards :
Number crunching :
ATI GPU app 0.19f fixes the ps_sgr_208_3s errors
(Message 28477)
Posted 28 Jul 2009 by Copycat-Digital for WCG* Post: ATI GPU app 0.19f is always running "high priority" This causes that the CPU app running on the same PC is limited to only 2 cores I tries to fix it with "<cmdline>n1</cmdline>" Only the number of CPUs specified in <cmdline>n(x)</cmdline> runs active while 18 WUs show that they are running but is waiting for a GPU Im running boinc 5.4.7 and tried 6.6.36 with no luck Is there a fix for this? Win XP Pro (32) sp3 CPU = Q8200 quad 4 Gb memory 1 x ATI 4500 (Cat 812) Boinc 5.4.7 |
4)
Message boards :
Number crunching :
Where's CUDA?
(Message 26937)
Posted 2 Jul 2009 by Copycat-Digital for WCG* Post:
Still camping. Maybe someone should send a search party :) |
5)
Message boards :
Number crunching :
64 CPUs on a Q6600 ????
(Message 25766)
Posted 17 Jun 2009 by Copycat-Digital for WCG* Post: "....and with a full cache of 64 x 6 workunits in progress!" You are quite right - I only looked at the first 2 pages. The computers are visible here |
6)
Message boards :
Number crunching :
64 CPUs on a Q6600 ????
(Message 25725)
Posted 16 Jun 2009 by Copycat-Digital for WCG* Post: But who would put vista on a server?! I have a friend - a builder - he used run it on his concrete mixer but then he discovered that mixing concrete with man-power is quicker and produce a better quality concrete :) PS He tried a demo/beta of Win7 but it only works if he replaces the 2 cylinder engine with a V8 |
7)
Message boards :
Number crunching :
64 CPUs on a Q6600 ????
(Message 25702)
Posted 16 Jun 2009 by Copycat-Digital for WCG* Post: A server possibly? OK a motherboard with 16 Q6600 CPUs - but what is the then: "GenuineIntel Intel(R) Core(TM)2 Duo CPU P8600 @ 2.40GHz [Intel64 Family 6 Model 23 Stepping 6] (64 processors) Microsoft Windows Vista Ultimate x64 Edition, Service Pack 2, v.275, (06.00.6002.00) 20 May 2009 20:01:38 UTC" 32 Core 2 Duo CPUs in 1 server? |
8)
Message boards :
Number crunching :
64 CPUs on a Q6600 ????
(Message 25691)
Posted 16 Jun 2009 by Copycat-Digital for WCG* Post: I noticed an user running 8 hosts. 5 Hosts reports 64 CPUs with Vista X64 - and with a full cache of 64 x 6 workunits in progress! How is this possible? Example: "GenuineIntel Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz [Intel64 Family 6 Model 15 Stepping 11] (64 processors) NVIDIA GeForce GTX 260 (896MB) Microsoft Windows Vista Ultimate x64 Edition, Service Pack 2, v.275, (06.00.6002.00) 14 Jun 2009 15:5" |
9)
Message boards :
Number crunching :
Work Availability v2 (June 9)
(Message 24719)
Posted 9 Jun 2009 by Copycat-Digital for WCG* Post: My turn to complain Can't keep the ATIs cool! Thanx Travis! |
10)
Message boards :
Number crunching :
ps_sgr_235_3s errors remain
(Message 24603)
Posted 8 Jun 2009 by Copycat-Digital for WCG* Post: Even with the fixed ATI app, I'm still getting errors on the 3s work. Here is one from an Intel: Task ID 75479248 Name ps_sgr_235_3s_4_124_1244493002_1 Workunit 74342510 Created 8 Jun 2009 20:33:36 UTC Sent 8 Jun 2009 20:35:48 UTC Received 8 Jun 2009 20:47:04 UTC Server state Over Outcome Success Client state Done Exit status 0 (0x0) Computer ID 40456 Report deadline 11 Jun 2009 20:35:48 UTC CPU time 0 stderr out <core_client_version>6.5.0</core_client_version> <![CDATA[ <stderr_txt> Running Milkyway@home ATI GPU application version 0.19f by Gipsel CPU: Intel(R) Core(TM)2 Quad CPU Q8200 @ 2.33GHz (4 cores/threads) 2.76509 GHz (146ms) CAL Runtime: 1.3.145 Found 1 CAL device Device 0: ATI Radeon HD 4800 (RV770) 512 MB local RAM (remote 28 MB cached + 256 MB uncached) GPU core clock: 650 MHz, memory clock: 993 MHz 800 shader units organized in 10 SIMDs with 16 VLIW units (5-issue), wavefront size 64 threads supporting double precision 0 WUs already running on GPU 0 Starting WU on GPU 0 main integral, 0 iterations predicted runtime per iteration is 0 ms (33.3333 ms are allowed) borders of the domains at 0 0 WU not compatible, falling back to a somewhat slow CPU code. Calculated about 0 floatingpoint ops on FPU. probability calculation (stars) Calculated about 1.44918e+007 floatingpoint ops on FPU. WU completed. CPU time: 0.21875 seconds, GPU time: 0 seconds, wall clock time: 0.236 seconds, CPU frequency: 2.76515 GHz </stderr_txt> ]]> Validate state Invalid Claimed credit 0 Granted credit 0 application version 0.19 |
11)
Message boards :
Number crunching :
Work Availability?
(Message 24080)
Posted 3 Jun 2009 by Copycat-Digital for WCG* Post: Keep in mind 3 things happened: 1) There was a minor server outage 2) The request was changed from 6 to 60 seconds 3) The very small ps_sgr_208_* runs My humble opinion is that the "ps_sgr_208_*" runs is the culprit causing an increase to the network traffic because of its very short run-time |
12)
Message boards :
Number crunching :
Work Availability?
(Message 24071)
Posted 3 Jun 2009 by Copycat-Digital for WCG* Post: I’ve been monitoring work allocated since the change PC1 Core 2 duo (SSSE3 0.19 XP Pro SP3) no GPU no change in workflow PC2 Core 2 Duo (0.19_ATI_SSE2e.exe XP Pro SP3 ATI 8.12) 4830 50% down PC3 Core 2 Quad (0.19_ATI_SSE2e.exe XP Pro SP3 ATI 8.12) 4850 30% down The bigger cache of WUs (6 x CPU = 24) on the quad makes the difference All PCs running Boinc 6.50 I’m not running a script but XP’s advance scheduler to update MW every 2 minutes to avoid the 2 hour delay after a few “Scheduler request completed: got 0 new tasks” However this happens now more frequently (28 times the past 6 hours) 2009/06/03 16:43:22 PM|Milkyway@home|Sending scheduler request: Requested by user. Requesting 14512 seconds of work, reporting 0 completed tasks 2009/06/03 16:48:26 PM||Project communication failed: attempting access to reference site 2009/06/03 16:48:28 PM|Milkyway@home|Scheduler request failed: Timeout was reached When this happens the scheduler waits for 5 minutes for the timeout before asking for work again A manual update does not help – stop & restarting Boinc is the only way to reset the counter |
13)
Message boards :
Number crunching :
Work Availability?
(Message 23938)
Posted 2 Jun 2009 by Copycat-Digital for WCG* Post: [quote] I hope the 6 WUs per cpu will go away at milkyway_gpu@home At the moment an i7 with a 4830 does more work than a Core 2 Duo with a 4870 - speed does not count but the bigger cache of WUs the i7 receive makes a big difference |
14)
Message boards :
Number crunching :
Servers down for maintenance or what?
(Message 22695)
Posted 19 May 2009 by Copycat-Digital for WCG* Post: Scheduler list received back after request OK till yesterday when the server went down. No scheduler list master file return received since last night. Trying manual update without response from server and get sometimes: Internet access OK. Server may be down. Scheduler list from SETI, CPDN & WCG running normally so it can't be my link. |
15)
Message boards :
Number crunching :
Servers down for maintenance or what?
(Message 22691)
Posted 19 May 2009 by Copycat-Digital for WCG* Post: Are there still problems? Server status shows all running – 31k + in progress I can log in to my account – I can post on this page - but - Can’t get to MW home page: (http://milkyway.cs.rpi.edu/milkyway/) Just get: Unable to connect to database - please try again later Error: 2002Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2) And Just get 2009/05/19 11:33:05 PM|Milkyway@home|Fetching scheduler list 2009/05/19 11:34:15 PM|Milkyway@home|Fetching scheduler list 2009/05/19 11:35:31 PM|Milkyway@home|Fetching scheduler list 2009/05/19 11:43:41 PM|Milkyway@home|Fetching scheduler list 2009/05/19 11:55:51 PM|Milkyway@home|Fetching scheduler list 2009/05/19 12:34:01 PM|Milkyway@home|Fetching scheduler list When requesting work Work form other projects running fine! |
16)
Message boards :
Number crunching :
MilkyWay_GPU - Almost There!
(Message 22311)
Posted 15 May 2009 by Copycat-Digital for WCG* Post: I’m trying something different to get news Set up a PC with SETI Maybe there is a transmission from Dave or Travis out of the black hole that sucked them up :-) |
17)
Message boards :
Number crunching :
MilkyWay_GPU - Almost There!
(Message 21692)
Posted 9 May 2009 by Copycat-Digital for WCG* Post:
If this is true then he must be running another MW in a parallel time zone. If someone could find a link to this time-zone then – maybe there will be work units there to download :) |
18)
Message boards :
Number crunching :
WUs distribution
(Message 21413)
Posted 6 May 2009 by Copycat-Digital for WCG* Post: I think that we all overlooking the fact that work units are allocated 6 per cpu- core. This is totally irrelevant to the crunching capacity of your GPU. So you can script or manually refresh till you are blue in the face. A 3850 installed in an i7 will earn more than a 4890 in a dual because the i7 will get 48 work units and the dual only 12 |
19)
Message boards :
Number crunching :
MilkyWay_GPU
(Message 19133)
Posted 17 Apr 2009 by Copycat-Digital for WCG* Post: Congrats ICE on No 1 |
20)
Message boards :
Number crunching :
3rd.in - optimized apps
(Message 17809)
Posted 7 Apr 2009 by Copycat-Digital for WCG* Post: [/quote] Nothing new then :/ [/quote] Only news is the ongoing fight who should get the biggest slice of the pizza. I look like BOINC cut down on the amount Cr's MW can hand out if you look at this graph No comment or news from Travis for the past 10 days |
©2024 Astroinformatics Group