[MRD]

Ok, check this out:

[mrd@localhost ~]$ glxgears
779 frames in 5.0 seconds = 155.800 FPS
915 frames in 5.0 seconds = 183.000 FPS
921 frames in 5.0 seconds = 184.200 FPS
4254 frames in 5.0 seconds = 850.800 FPS
62369 frames in 5.0 seconds = 12473.800 FPS
48891 frames in 5.0 seconds = 9778.200 FPS
48894 frames in 5.0 seconds = 9778.800 FPS
48732 frames in 5.0 seconds = 9746.400 FPS
31734 frames in 5.0 seconds = 6346.800 FPS
26640 frames in 5.0 seconds = 5328.000 FPS
48859 frames in 5.0 seconds = 9771.800 FPS
47074 frames in 5.0 seconds = 9414.800 FPS
48892 frames in 5.0 seconds = 9778.400 FPS
23661 frames in 5.0 seconds = 4732.200 FPS
1412 frames in 5.0 seconds = 282.400 FPS
919 frames in 5.0 seconds = 183.800 FPS
873 frames in 5.0 seconds = 174.600 FPS

During the course of running glxgears, I stopped and then restarted F@H. Whenever I run it with F@H running, my fps drops from like 9750 fps to like 150 fps.

Is there anything I can do to prevent this besides not folding?

[overdoze]

are you talking about linux. I have a script to stop the folding midway and resume after a regular job is finish. It has a 30 seconds time window for every check.

EDIT: I am running jobs at my linux servers regularly and Folding affect the performance of my jobs runtime a lot. I have post the problem in folding community but noone seems to care. Therefore, I wrote the script to prevent folding to take away my resource when I need it. I only see this problem in Linux OS however.

[MRD]

Let me play around with priorities a bit first and see if that works.