Posts by Nasicus
log in
1) Message boards : Number crunching : MilkyWay_GPU - Almost There! (Message 22830)
Posted 20 May 2009 by Nasicus
Travis wrote:
currently it's crunching the current stripe 82 WUs in around a minute using a GeForce 9600M GT.


Nasicus wrote:

At the moment I'm using an ATI with app_info for Milkyway and a nVidia for GPUgrid in the same PC. Will it be possible to use an ATI card and a nVidia card at the same time for Milkyway?


How exciting. That's the card I have in my laptop - will it share with GPUGRID ?

Probably this card will work. You should expect durations of 24h to more than 50h for the GPUgrid WUs on this 9600M GT which has 32 shaders (on my 8800GTS 512 with 128 shaders they take about 10 to 16 hours). But this are only estimations as I don't have a 9600M GT.
2) Message boards : Number crunching : MilkyWay_GPU - Almost There! (Message 22825)
Posted 20 May 2009 by Nasicus
But this way I could be sure that I can use my CPU, the ATI and the nVidia all in one PC at the same time for Milkyway ;-)
3) Message boards : Number crunching : MilkyWay_GPU - Almost There! (Message 22812)
Posted 20 May 2009 by Nasicus
At the moment I'm using an ATI with app_info for Milkyway and a nVidia for GPUgrid in the same PC. Will it be possible to use an ATI card and a nVidia card at the same time for Milkyway?
4) Message boards : Number crunching : 3rd.in - optimized apps (Message 15558)
Posted 15 Mar 2009 by Nasicus
CPU frequency: 2.40003 GHz :-)

BTW: the CPU frequency reported is not correct, according to CPU-Z it is running at 3.249 GHz

I bet you are overclocking with a tool under windows and not through the BIOS.

You won ;-)

Actually that is some kind of design flaw of the Windows high performance counters used to measure times with ┬Ás resolution. You could add the switch /usepmtimer to the boot.ini to correct that. But in case of the MW apps it is purely cosmetic.

I will try that, just for fun. Thanks.
5) Message boards : Number crunching : 3rd.in - optimized apps (Message 15481)
Posted 15 Mar 2009 by Nasicus
Upped the clock to 615 MHz and guess what --
My 1st sub 1sec wu !!!!! http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=23350847


But only CPU time. It took your GPU more than 30 seconds to crunch this WU.

Yes, I must admit that the consept of CPU/GPU crunching took a while for me to get my head around. Doesn't really matter if the CPU takes a millionth of a second - it's the GPU that's doing the work and taking the time.

None-the-less, sub 1 seconds may be a rare thing (at least catching one to record it) - so congratulations Copycat-Digital! :)

It is a nice demonstration of the low CPU load.
But I would like to report GPU time as WU time in the next version as this is a much better representation of the time the WUs actually take. Only Travis has to agree with that. But he was quite quiet the last days, maybe still the flu?

Indeed, great app. Thanks a lot, good work.
Found this result (running three results concurrently):
CPU time: 0.796875 seconds, GPU time: 27.125 seconds, wall clock time: 133.139 seconds, CPU frequency: 2.40003 GHz :-)

BTW: the CPU frequency reported is not correct, according to CPU-Z it is running at 3.249 GHz
6) Message boards : Number crunching : ATI help please. (Message 13786)
Posted 3 Mar 2009 by Nasicus
First I had a nVidia 8800GTS512 installed, then an ATI 4850. And I changed them a few times. It's just a shutdown, change the cards and start again. Yes, it works ;-)

Mike
7) Message boards : Number crunching : Poll: How much credit do you think is fair? (Message 2676)
Posted 24 Mar 2008 by Nasicus
4




Main page · Your account · Message boards


Copyright © 2017 AstroInformatics Group