| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: Help Conquer Cancer
Thread: It's as bad as the beta |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 96
|
|
| Author |
|
|
nanoprobe
Master Cruncher Classified Joined: Aug 29, 2008 Post Count: 2998 Status: Offline Project Badges: 
|
Am starting to wonder if the lag is dependant on type of monitor and how its hooked up to the pc. My 5670 has a 21 inch monitor attached by VGA with little lag. My 6950 has a 24 inch dell using display port with allot of lag. When I get time, will change to HDMI to see if anything changes. For those having lag, how is your monitor attached? May also depend on the refresh rate. Mine are older monitors @ 60Hz. The newer ones can be 75Hz+.
In 1969 I took an oath to defend and protect the U S Constitution against all enemies, both foreign and Domestic. There was no expiration date.
  |
||
|
|
Simplex0
Advanced Cruncher Sweden Joined: Aug 14, 2008 Post Count: 83 Status: Offline Project Badges: 
|
I have an Asus 24" VS248H 1920x1080 2ms DVI/HDMI LED monitor connected to an KVM switch using HBD-15 connectors so I can use the same monitor, keyboard & mouse to control 2 computers.
|
||
|
|
mmstick
Senior Cruncher Joined: Aug 19, 2010 Post Count: 151 Status: Offline Project Badges: 
|
It has nothing to do with the monitor you use, it has to do with the level of power of your graphics card. If your graphics card is weaker than 7800 series it will induce lag when running until you use an app_info file to change the default settings to give the desktop more time to refresh. The app sends data to be processed by the GPU and does not allow your OS to refresh the screen until it is completed. The time between completion of these chunks of data is longer on weaker cards, so the lag is more evident on weaker graphics cards.
----------------------------------------[Edit 1 times, last edit by mmstick at Oct 15, 2012 4:57:57 PM] |
||
|
|
Bearcat
Master Cruncher USA Joined: Jan 6, 2007 Post Count: 2803 Status: Offline Project Badges: 
|
It has nothing to do with the monitor you use, it has to do with the level of power of your graphics card. If your graphics card is weaker than 7800 series it will induce lag when running until you use an app_info file to change the default settings to give the desktop more time to refresh. The app sends data to be processed by the GPU and does not allow your OS to refresh the screen until it is completed. The time between completion of these chunks of data is longer on weaker cards, so the lag is more evident on weaker graphics cards. It would have allot to do with lag. VGA and a small monitor doesn't require much power or signal for refresh from a GPU to drive the monitor. HDMI or display port and a HD or say a 24 inch monitor or bigger requires allot more power to be driven from a GPU. But this is only half the issue as the software from WCG is different from other dedicated GPU projects. I don't have 1/10th the issues running milkey way as I do here. Being WCG's first project with the GPU, am sure it will be refined as those other projects have done. Just will take some time and growing pains. Until then, just live with it or crunch another project. I'll live with it as it's worth it. Thanks for your insight.
Crunching for humanity since 2007!
 |
||
|
|
mmstick
Senior Cruncher Joined: Aug 19, 2010 Post Count: 151 Status: Offline Project Badges:
|
It has nothing to do with the monitor you use, it has to do with the level of power of your graphics card. If your graphics card is weaker than 7800 series it will induce lag when running until you use an app_info file to change the default settings to give the desktop more time to refresh. The app sends data to be processed by the GPU and does not allow your OS to refresh the screen until it is completed. The time between completion of these chunks of data is longer on weaker cards, so the lag is more evident on weaker graphics cards. It would have allot to do with lag. VGA and a small monitor doesn't require much power or signal for refresh from a GPU to drive the monitor. HDMI or display port and a HD or say a 24 inch monitor or bigger requires allot more power to be driven from a GPU. But this is only half the issue as the software from WCG is different from other dedicated GPU projects. I don't have 1/10th the issues running milkey way as I do here. Being WCG's first project with the GPU, am sure it will be refined as those other projects have done. Just will take some time and growing pains. Until then, just live with it or crunch another project. I'll live with it as it's worth it. Thanks for your insight. Please take some IT courses like I have then try and say that again. The size of the monitor or the type of video connector have nothing to do with this, nor the graphics cards ability to refresh the screen. What you may be trying to say is that the maximum refresh rate of a monitor depends on the type of connector used, the length of the cable, and the resolution of the screen, but that has no relationship with your graphics cards ability to refresh the screen. If there is no frame to send to begin with, you will not get a screen update, regardless of what kind of monitor or video port is being used. You don't have any problems with MilkyWay@Home, or other projects, even when I use diablominer to use 100% GPU at all times (and utilize my 7950 during idle portions of HCC), because these programs were designed to take into account to make sure the OS can have time to refresh the screen by opening slots in the internal queue so that the driver will refresh the screen during these times. They have much lower default settings than HCC does. If you use an app_info with commands to change the gpu polling and frequency rates you will get the same responsiveness you enjoy in MilkyWay. |
||
|
|
JacobKlein
Cruncher Joined: Aug 21, 2007 Post Count: 21 Status: Offline |
mmstick, I agree that this has nothing to do with how beefy your card is, or how your monitor is connected, or even how much % GPU is being used. I'm a software developer, and believe the problem is as you said -- the way the application interacts with the GPU (on some architectures, possibly only nVidia)... does not allot enough time/resources for the OS to be able to refresh itself properly.
The problem is most-noticeable when watching a video, or moving a Window around. I'm curious though, you mention the ability to adjust gpu polling and frequency using the Anonymous Platform app_info... but I can't seem to get that to work. Do you have an example app_info file that works? If it involves passing command line arguments, can you actually see those arguments listed in Task Manager's Process tab column Command-line? I've yet to see any app_info workaround actually mitigate this WCG issue. |
||
|
|
mmstick
Senior Cruncher Joined: Aug 19, 2010 Post Count: 151 Status: Offline Project Badges:
|
<cmdline> ----gpu-target-frequency 60 gpu-polling-mode 16</cmdline>
This sets the polling and frequency that BOINC will use on this project app, the lower the numbers the better it will utilize the GPU (and less responsive it will be to the user), the higher the more times your GPU will have of doing other things like refreshing the screen, rendering video content, etc. You'll have to test for what suits your graphics card the best. |
||
|
|
JacobKlein
Cruncher Joined: Aug 21, 2007 Post Count: 21 Status: Offline |
Can you actually see those arguments listed in Task Manager's Processes tab under column "Command line"?
----------------------------------------Also, are you sure those aren't Milky-Way-specific command line options? When I use your <cmdline> tag outside of the <coproc> tag, it feeds the arguments to the app and it fails immediately with Computation Error. I have a feeling that you are spouting incorrect advice as fact, and encourage you to make sure your suggestions are viable before posting. If you actually have managed to get those arguments passed, then I apologize and will need more details on how to get it to work so I can see the arguments in Task Manager. [Edit 3 times, last edit by JacobKlein at Oct 15, 2012 8:23:14 PM] |
||
|
|
mmstick
Senior Cruncher Joined: Aug 19, 2010 Post Count: 151 Status: Offline Project Badges:
|
You'll have to locate the user who is using the commands as per the specifics he uses. He is probably located somewhere along the "HCC GPU APP HAS LAUNCHED." thread.
I am not spouting incorrect advice, so please refrain from insinuating such. If you believe I am, please prove it. I haven't personally needed to modify my app_info aside from configuring to use four work units instead of one, as my 7950 does not have any problems with refreshing the screen. |
||
|
|
JacobKlein
Cruncher Joined: Aug 21, 2007 Post Count: 21 Status: Offline |
mmstick,
----------------------------------------Can you please see if you can get those command line arguments to actually function, and show in Task Manager? [Edit 1 times, last edit by JacobKlein at Oct 15, 2012 9:02:08 PM] |
||
|
|
|