Forum > GPU crunching
Driver, application and VRAM requirement?
Miep:
--- Quote from: Raistmer on 27 Jul 2010, 01:36:34 am ---
--- Quote from: Miep on 27 Jul 2010, 01:33:08 am ---
Is there anything in stderr to check which dlls were used?
--- End quote ---
I'm afraid not.
Since 2.3 there was not such big speed improvement so probably with 2.3 DLLs you reached peak GPU performance until V13/CUDA 3.1 app will be introduced to public.
--- End quote ---
Thanks, much obliged.
I thought there wasn't, since I couldn't see anything but you can always have 'tomatoes on your eyes' - I'm not awake enough to translate german proverbs.
I'll throw the 3.0 dll in there anyway, if only to check the memory uptake.
Jason G:
--- Quote from: Miep on 27 Jul 2010, 01:33:08 am ---That ran like a treat. And the increase in speed with the higher dlls is remarkable.
Of the 3 tasks that ran O/N 1 has validated and 2 are waiting for wingman. (for reference: valid pending pending)
Is there anything in stderr to check which dlls were used?
--- End quote ---
I just realised you're running Vista (That'll teach me to look properly, and make proper connections ::)). The newer series of drivers are Microsoft's WDDM driver model based, which uses a paged scheme for memory management where each application sees its own full address range. That is opposed to XP drivers physical video memory model which was prone to fragmentation & shared the video memory as one block. IMO with the new drivers under Vista you *should* have no low memory issues running any of the newest builds (Though experimental Cuda 3.0 & 3.1 builds still to be determined ...*hint* *hint*)
Jason
Miep:
--- Quote from: Jason G on 27 Jul 2010, 01:43:31 am ---
I just realised you're running Vista (That'll teach me to look properly, and make proper connections ::)). The newer series of drivers are Microsoft's WDDM driver model based, which uses a paged scheme for memory management where each application sees its own full address range. That is opposed to XP drivers physical video memory model which was prone to fragmentation & shared the video memory as one block. IMO with the new drivers under Vista you *should* have no low memory issues running any of the newest builds (Though experimental Cuda 3.0 & 3.1 builds still to be determined ...*hint* *hint*)
Jason
--- End quote ---
Hmm good point. I was going to say I tried V12 on 257.21, but now I'm not sure. Will have to check the logs. Edit: I didn't. Only 195.62 and 258.98 got tested with the variuos dll's (3.x still pending).
One thing after the other Jason... no need to pull out fenceposts for waving ;)
Raistmer:
If GPU memory paging occurs you should not only check is it works or not but elapsed/cpu times too.
GPU memory swap could be performance killer (or not ).
Miep:
Todays O/N run just got reserved for Jason's *hint* *hint* fencepost.
daytime and O/N run Wu runtimes are not very comparable on my system. daytime will see a number of restarts, depending on how much idle time arises, O/N can run uniterreupted.
Also cooling and resulting throttling are different at work and at home. (the office has A/C but the gap between notebook and table is smaller)
I can note down elapsed, cpu and AR on the diffrent builds, dlls and environments, if you want me to. (and any other easily accessible parameter)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version