- Apr 17, 2008
- 23
- 0
- 0
Hello!
The by far most commonly used SLI/CrossFire mode is alternate frame rendering, where one card draws all odd, and the other one all even frames.
So if a scene is for example rendered with 30 FPS, every frame takes ~33.3 ms to update and we should get something like the following frame times:
But how does these 30 FPS look like when the scene is rendered using SLI or CrossFire?
In this example, every even frame takes around 56.5 ms to update, which is almost 70% longer than expected!
The frame rate says ~30 FPS, but in reality every second frame is updated with a rate of only ~17.8 FPS!
This problem becomes very noticeable at low frame rates of course.
You can test this on your own quite easily by logging the frame times with a tool like Fraps.
Driver versions, SLI/CrossFire compatibility flags and the kind of the Windows OS has no impact on the problem.
The issue exists since SLI/CrossFire got on the market and has already been under discussion in German forums for a while and was reproduced by all SLI/CrossFire users there.
There is even a German speaking article that demonstrates the problem with a video.
I think that this is quite a scandal and that it is in the interest of the whole enthusiast market to make this public, so that ATI/Nvidia finally delivers a solution for this.
Thanks for your support on this!
The by far most commonly used SLI/CrossFire mode is alternate frame rendering, where one card draws all odd, and the other one all even frames.
So if a scene is for example rendered with 30 FPS, every frame takes ~33.3 ms to update and we should get something like the following frame times:
This also is what 30 FPS look like on a single card setup.WHAT 30 FPS SHOULD LOOK LIKE
Frame, Time (ms)
1, 0.000
2, 33.3
3, 66.6
4, 99.9
5, 133.2
6, 166.5
7, 199.8
8, 233.1
9, 266.4
10, 299.7
But how does these 30 FPS look like when the scene is rendered using SLI or CrossFire?
Every odd frame number takes much less than the expected 33.3 ms to update and every even frame takes much longer to update.WHAT 30 FPS DO LOOK LIKE WITH SLI/CROSSFIRE
Frame, Time (ms)
1, 0.000
2, 12.1
3, 68.3
4, 80.5
5, 136.8
6, 148.9
7, 205.1
8, 217.3
9, 273.7
10, 285.7
In this example, every even frame takes around 56.5 ms to update, which is almost 70% longer than expected!
The frame rate says ~30 FPS, but in reality every second frame is updated with a rate of only ~17.8 FPS!
This problem becomes very noticeable at low frame rates of course.
You can test this on your own quite easily by logging the frame times with a tool like Fraps.
Driver versions, SLI/CrossFire compatibility flags and the kind of the Windows OS has no impact on the problem.
The issue exists since SLI/CrossFire got on the market and has already been under discussion in German forums for a while and was reproduced by all SLI/CrossFire users there.
There is even a German speaking article that demonstrates the problem with a video.
I think that this is quite a scandal and that it is in the interest of the whole enthusiast market to make this public, so that ATI/Nvidia finally delivers a solution for this.
Thanks for your support on this!