Posts by coldFuSion

1) Message boards : News : monitor suspend/resume bug in 295/296 drivers (Message 24138) Posted 24 Mar 2012 by coldFuSion Post: Win 7 64-bit (SP1) Dual GTX 580s Driver: 295.73 Power Control Panel -> Turn off the display: Never Result: no errors
2) Message boards : News : monitor suspend/resume bug in 295/296 drivers (Message 23681) Posted 28 Feb 2012 by coldFuSion Post: The message threads over at SETI seem to indicate its the windows driver that has the issue. It has been reported by people using a DVI connected monitor, not sure if a VGA connected monitor also has the problems. It depends on the card and if they are using a DVI to VGA adaptor. I use the HDMI connector on my GTX 580's and the issue affected me using both 295.51 beta and 295.73 WHQL drivers. I have configured power settings to never turn off the monitor and have since completed 4 tasks in a row successfully.
3) Message boards : Graphics cards (GPUs) : New Beta Nvidia Drivers (Message 23617) Posted 23 Feb 2012 by coldFuSion Post: Several WUs error out with the latest beta drivers. Got several WUs error out with the latest WHQL 295.73 too ! I just come back to 290.53 drivers. Had several errors with the 295.51 beta drivers and now with the 295.73 WHQL drivers too. Beta 290.53 and lower seem fine. Here is my Windows Application Event log Faulting application name: acemdlong_6.15_windows_intelx86__cuda31, version: 0.0.0.0, time stamp: 0x4e11af1b Faulting module name: acemdlong_6.15_windows_intelx86__cuda31, version: 0.0.0.0, time stamp: 0x4e11af1b Exception code: 0x40000015 Fault offset: 0x0003af9a Faulting process id: 0x1368 Faulting application start time: 0x01ccf1ae8797b3c6 Faulting application path: C:\ProgramData\BOINC\projects\www.gpugrid.net\acemdlong_6.15_windows_intelx86__cuda31 Faulting module path: C:\ProgramData\BOINC\projects\www.gpugrid.net\acemdlong_6.15_windows_intelx86__cuda31 Report Id: c619037a-5da1-11e1-aa23-50e5493a576e
4) Message boards : Graphics cards (GPUs) : 65nm GTX260-216 issue. (Message 18616) Posted 10 Sep 2010 by coldFuSion Post: It's also possible that the stock GPU voltage is insufficient I had this problem with my GTX 470 You could try using MSI Afterburner to up the GPU voltage one notch at a time and see if it stabilizes it.
5) Message boards : Graphics cards (GPUs) : acemd2 611 cuda3.1 for Fermi (Message 18171) Posted 26 Jul 2010 by coldFuSion Post: Looks like, my 480 cards running on Win 7, are around 30% to 40% faster on acemd2 611 compared to 605, which means that it is, on average, slightly faster than a 285 card running on win xp. This is a good improvement, but 480 should really be twice as fast as 285, since it has double the cores. So the drivers for these cards, still need to be updated. Apples to oranges You can't really make a comparison to a new card running on Win7 to an older card running on WinXP The drivers on Win7 don't need to be "updated" M$ needs to abandon WDDM which has unacceptable overhead that directly and significantly affects performance. IMHO
6) Message boards : Graphics cards (GPUs) : acemd2 611 cuda3.1 for Fermi (Message 18115) Posted 21 Jul 2010 by coldFuSion Post: I have seen some very significant improvement in a few specific WUs. However I thought I would post results from one of the seemingly least efficient WUs I have run: IBUCH_freebind_pYEEI_100706. This one only pushes my GPU usage into the 70 something percent. 2670817 16,609.06 16,413.48 7,954.42 11,931.63 ACEMD2: GPU molecular dynamics v6.05 (cuda30) 13.284 ms/step 2701432 15,484.38 15,454.58 7,954.42 11,931.63 ACEMD2: GPU molecular dynamics v6.11 (cuda31) 12.385 ms/step That's approximately a 7% improvement.
7) Message boards : Graphics cards (GPUs) : acemd2 611 cuda3.1 for Fermi (Message 18093) Posted 20 Jul 2010 by coldFuSion Post: My card finish v6.11 under Win7 http://www.gpugrid.net/result.php?resultid=2696901 ACEMD2: GPU molecular dynamics v6.11 (cuda31) http://www.gpugrid.net/result.php?resultid=2692327 ACEMD2: GPU molecular dynamics v6.05 (cuda30) That's about a 40% improvement O_O
8) Message boards : Number crunching : vitesse de calcul gtx 260/gtx 470 (Message 18030) Posted 17 Jul 2010 by coldFuSion Post: Hello I'll buy a ZOTAC GTX 470 Amp edition soon and I wanted to know how much I can expect to gain in computing time compared to my current gtx 260? thank you According to this thread comparing GFlops of the various NVIDIA GPUs http://www.gpugrid.net/forum_thread.php?id=1150&nowrap=true#18027 It looks like you could realize twice the BOINC crunching performance vs a GTX260. Nice looking custom designed card If anyone is interested in seeing what this bad boy looks like here is a link http://pden.zotac.com/index.php?page=shop.product_details&category_id=119&flypage=flypage_images.tpl&product_id=257&option=com_virtuemart&Itemid=1
9) Message boards : Graphics cards (GPUs) : ACEMD2 CUDA3.1 is now out (Message 18029) Posted 17 Jul 2010 by coldFuSion Post: GTX470 on XP running a Beta: 2678845 1704781 17 Jul 2010 8:32:57 UTC 17 Jul 2010 11:05:25 UTC Completed and validated 280.06 276.80 187.28 280.92 ACEMD beta version v6.32 (cuda31) Nearly identical results on my OCed GTX470 on XP 2681352 1706384 17 Jul 2010 15:17:24 UTC 17 Jul 2010 15:36:53 UTC Completed and validated 269.16 266.86 187.28 280.92 ACEMD beta version v6.32 (cuda31) Time per step: 5.344 ms
10) Message boards : Graphics cards (GPUs) : Swan_Sync=0 and GTX 470 results: is this slow? (Message 17990) Posted 15 Jul 2010 by coldFuSion Post: Nothing critical needs changing that I am aware of...unless you are in fact running too hot or something. However i do suggest setting Boinc Manager -> Advanced -> Preferences -> Network usage (tab) -> Additional Work Buffer -> 0.01 That way your client doesn't download and hold additional jobs too early. This will ensure you take advantage of and receive the quick turnaround bonus credits.
11) Message boards : Graphics cards (GPUs) : Swan_Sync=0 and GTX 470 results: is this slow? (Message 17984) Posted 15 Jul 2010 by coldFuSion Post: Unfortunately you have run smack into the WDDM overhead issue Noticeably slower in gaming and crippling slower in high performance GPU computing like GPUGRID. I still can't comprehend how Microsoft much less anyone else finds it acceptable that the new graphic driver architecture is slower. But that's a topic for another thread Suffice to say there is nothing you can do short of crunching on Linux or XP as already suggested to realize better productivity.
12) Message boards : Graphics cards (GPUs) : ACEMD2 CUDA3.1 is now out (Message 17982) Posted 15 Jul 2010 by coldFuSion Post: Same results on my GTX 470...immediate failure Sorry i can't post the error details ATM but I am fairly sure they identical to skgiven's
13) Message boards : Graphics cards (GPUs) : ACEMD2 CUDA3.1 is now out (Message 17857) Posted 4 Jul 2010 by coldFuSion Post: just want to suggest that everyone take a slow deep breath.... and remind everyone we are using bleeding edge drivers with bleeding edge developer tools. Let's not prematurely flee like rats from a sinking ship just because every single GPU transistor is not working at 100% optimization and productivity. Remember the main underlying goal is to help crunch protein simulations for medical research. If some work units are slower now than before...so what? GPU crunching is still exponentially faster than crunching the same thing on CPU based applications. If we keep our wits about us and work together we can help improve application productivity by providing constructive feedback.
14) Message boards : Graphics cards (GPUs) : ACEMD2 CUDA3.1 is now out (Message 17841) Posted 3 Jul 2010 by coldFuSion Post: Results seem to vary drastically with my WinXP I392-TONI_KIDln-12-100-RND6196_0 # Device 0: "GeForce GTX 470" SWAN: Using synchronization method 0 # Time per step (avg over 1300000 steps): 4.924 ms!!! # Approximate elapsed time for entire WU: 6401.594 s h232f99r440-TONI_CAPBINDsp2-25-100-RND7492_0 # Device 0: "GeForce GTX 470" SWAN: Using synchronization method 0 # Time per step (avg over 650000 steps): 16.178 ms # Approximate elapsed time for entire WU: 10515.719 s Not sure what the difference between these 2 applications is but if the second can be optimized like first then that would be seriously impressive
15) Message boards : Graphics cards (GPUs) : CUDA 3.1 has been released (Message 17806) Posted 1 Jul 2010 by coldFuSion Post: GTX470 OC 700/1400/1850 no SWAN_SYNC environment variable # Time per step (avg over 50000 steps): 6.745 ms # Approximate elapsed time for entire WU: 337.234 s
16) Message boards : News : For Nvidia Fermi users (Message 17768) Posted 30 Jun 2010 by coldFuSion Post: You only need to DL the developer drivers if you plan to do coding with the toolkit. For 99% of us we only need to install the latest WHQL drivers which has the support built-in for applications developed using the CUDA 3.1 toolkit
17) Message boards : News : For Nvidia Fermi users (Message 17760) Posted 29 Jun 2010 by coldFuSion Post: I too have a GTX470 which is OC (core/shaders/memory) to a GTX480 at reference specs Will be nice to squeeze out even more performance and credits.
18) Message boards : Server and website : Server and site back up and running (Message 17719) Posted 27 Jun 2010 by coldFuSion Post: welcome back GPUGRID :) Would be nice to know what happened pls Do that manual update of project everyone My back-off time was up to 11 hours =D
19) Message boards : Multicore CPUs : NEW (Message 17661) Posted 18 Jun 2010 by coldFuSion Post: While it's true that performance and productivity will never come close to GPU crunching I strongly believe the option for CPU crunching should be made available. Just make the CPU WUs smaller so that they don't take more than a day to crunch. IMHO folding@home is so successful and attracts so many people simply because they offer clients and WUs that can be processed on single core or multi-core CPUs as well as GPU based clients and WUs.
20) Message boards : News : Fermi application 6.73 is now out (Message 17408) Posted 28 May 2010 by coldFuSion Post: Change your GPUGrid Preferences so that you only have ACEMD2 selected. Could somebody check and clarify this advice, please? I've just set up a new GTX 470 (host 71413), and attached with preferences ACEMD: no ACEMD ver 2.0: yes ACEMD beta: no That got me a download of acemd2_6.03 with Cuda 2.2 DLLs - just the same as my 9800GTs. It failed (not unexpected). From the Applications page, I need v6.73 of 'Full-atom molecular dynamics', not 'ACEMD - GPU molecular dynamics' at all. It's all very confusing, even for an experienced user. I think you need to have ACEMD = yes and ACEMD ver 2.0 = no The advice you've seen above was a way to avoid these units if I've read correctly. I have none of these choices listed under my GPUGrid Preferences and my GTX 470 client is still running ACEMD2: GPU molecular dynamics v6.05 (cuda30) How do I access the WU choices?