Setting the clocks must be performed using the gui. You need to have
the Coolbits option in your xorg.conf. It reminds me to still update
nvclock which can do this from cli fine ;)
Roderick
On Tue, May 11, 2010 at 3:45 PM, Dan Kegel wrote:
> On Tue, May 11, 2010 at 1:27 AM, Roderick Colenbrander
On Tue, May 11, 2010 at 1:27 AM, Roderick Colenbrander
wrote:
> On my laptop I also had some weird results in some game depending on
> when I started it. In my case I suspected that the GPU wasn't at the
> maximum clock speeds yet. Depending on what GPU you are using you
> might also have '2d' and
On Tue, May 11, 2010 at 7:27 AM, Dan Kegel wrote:
> http://kegel.com/wine/yagmarkdata/wine-1.1.44-19-vs-wine-1.1.44-72.txt
> shows yesterday's wine's performance compared to today's.
> Highlights:
> Comparing wine-1.1.44-19 with wine-1.1.44-72
> benchmark_variable wine-1.1.44-19 wine-1.1.44
On Tue, May 11, 2010 at 3:27 PM, Dan Kegel wrote:
> Why does Wine return a slow result sometimes?
Solar flares! ;)
I can't stay I notice this discrepancy in actual game play day after
day though.
I personally would be looking at memory available as the cause. In
general you want to make sure y
http://kegel.com/wine/yagmarkdata/wine-1.1.44-19-vs-wine-1.1.44-72.txt
shows yesterday's wine's performance compared to today's.
Highlights:
Comparing wine-1.1.44-19 with wine-1.1.44-72
benchmark_variablewine-1.1.44-19 wine-1.1.44-72 ratio
3dmark06_3DMark_Score 3377.003388.00
