My system has always defaulted to an insanely high 256 clock AGP Latency whereas the PCI Latency is only 32. I'm now running with it at AGP Latency 32 and PCI Latency of 32. The system seems a LOT more responsive AND a lot better at multitasking. Minimizing/Maximizing windows and such no longer causes music playing in the background to briefly slow down or anything. In addition, my DIVX playback appears MUCH smoother than previously. Oh, one last thing... this also corrected a kind of bug I've always noticed with this system... For whatever reason when I'd, for example, right-click on the C drive icon from Start Menu/My Computer (I have My Computer set as a menu that comes off of Start Menu), I'd usually experience a graphical glitch where the part of the menu that overlapped the taskbar would remain over it even after the menu was gone. Refreshing the desktop wouldn't correct the glitch either. That problem seems to have been corrected by my changing the AGP latency from its default 256 down to 32. Anyhow, I just thought I'd pass that wisdom on...
Tedy, I'm actually referring to AGP Latency, not AGP Aperture. My AGP Aperture is currently set at 512 MB (half of my total RAM) though it rarely uses hardly any of it since my graphics card has 128 MB RAM onboard. I'm currently trying my system at AGP Latency 64 in addition to PCI Latency 64 since I've read online in various places that those are the ideal settings for best performance. I haven't run a 3DMark test on it quite yet... First I'm checking for stability and such...
Well, I've gone back to using the PCI latency of 32 in combination with the AGP latency being 32 and I have run a 3DMark to compare the 3D performance. I got roughly the same benchmark score with PCI latency at 32 / AGP latency at 32 as I had previously with the PCI latency at 32 / AGP latency at 256 (default). Although the scores were almost identical, the graphics still seemed smoother with the PCI/AGP latencies both set to 32. This may not be the case for everyone, however, due to differences in hardware, bios settings, driver versions, etc... Best to run some tests of your own to determine what works best for you...
I tried powerstrip up untill I noticed it took 50% CPU the second I clicked 3dmark...then proceeded to stay at 100% while the 3dmark window was open...gogo powerstrip
I tried powerstrip up untill I noticed it took 50% CPU the second I clicked 3dmark...then proceeded to stay at 100% while the 3dmark window was open...gogo powerstrip
Wow.. I never noticed that, wtf is up with that? I usally close powerstrip b4 I game so I never really checked. I only use powerstrip to change agp latency & it sticks if u close powerstrip after startup.
There has got to be another way to change the latecy...what about wpcredit? Does anyone know if the AGP latency is anywhere in it? We could just look at the before and after and then make the change ourself...
Tony420,
How did you get that to work? That was the first thing I tried! I am able to change the latency with the newest version of WPCREDIT, but was unable to make WPCRSET make the change upon reboot. I know the WPCRSET works since I've used it for altering other registers. For some reason, however, when I tell it BUS 2, DEV 0, FUN 0 and the offset 0D... It accepts it, but upon reboot when I look in WPCREDIT, the value is back to the default. Any ideas why WPCRSET is being a pain on this or is it somehow user error on my part???
It accepts it, but upon reboot when I look in WPCREDIT, the value is back to the default. Any ideas why WPCRSET is being a pain on this or is it somehow user error on my part??? :
I have same problem, I cant get WPCRSET v1.2 to set it on startup. It sets idle tweak (6F - 1F) fine. Tony420.. if u could check your wpcrset & maybe what version your using? Im using (& only version I can find) WPCRSET 1.20 & WPCREDIT 1.2a
Processors
Motherboards
Chipsets
Memory
Graphics Cards
Storage
Cases and Cooling
Mobile
Systems
Displays
Shows and Expos
Powerstrip > AGP Latency Change
Re: Powerstrip > AGP Latency Change
Linear Mode
