Question / Help 40% performance dip in graphical performance

S

Solkrieg

New Member
What is happening: I am playing Rainbow Six Siege and I get typically around 130 FPS, however when I have OBS recording/streaming I get 70-95FPS. I have acknowledged this is an OBS specific issue because I tested it out with xSplit (which I loath) and didn't get any change in performance. I did set it to software encoder too with the lowest preset for quality possible.

RIG:
Display: 3440x1440 90hz G-Sync
Processor: Thread Ripper 1950x
Graphics: 1080ti SLI
RAM: 64GB's
Storage: I am recording on separate storage from my game and OS.

Before I get a lot of "Why are you using your thread ripper for gaming" posts: I am using my thread ripper as two different 1900x's basically. I'm not using shared cache (causes latency) and Siege is a processor heavy game (for some reason). So I have 8 cores for Siege, which uses about 75% of each core, and OBS is using 16 threads. This was mostly a cost effective move because I wanted to save on buying extra components for a second streaming PC/capture card, etc.

OBS settings:
Screen capture (gives better performance than game capture, I believe because of G-sync)
Base canvas: 2560x1440
Scaled: 1280x720 (NOTE: Since I have an ultrawide, I am centering my screen and basically cutting off the ultrawide sides where "black bars" would be)
FPS: 60
Encorder: x264
RC: CBR
Bitrate: 7000
Buffer size: 14000
Keyframe: 0
CPU usage preset: slow
profile: Main
Tune: Film

LOG: https://gist.github.com/anonymous/27ae0c7aa84a6d648734c7c42126eabd

Please note: I also have tried NVENC recording and I do get a higher performance however it's negligible and nowhere near worth it considering the quality is much lower. I have also tried using the "SLI" option under game capture/screen capture with much, much worse results.
 
Have you tried with the second video card physically removed?
Have you made sure the nvidia in-game overlay is turned off?
 
last time, I tried anything lower than ultrafast in XSplit, it was not comparable to OBS.
Xsplit preset "medium" was not using the same x264 compression features as OBS "medium", that's why in my test, the CPU load was way lower in Xsplit (as was the compression effeciency).

Maybe you can analyze both recordings and check, that they use at least the same ref- and b-frames.
 
BK-Morpheus said:
last time, I tried anything lower than ultrafast in XSplit, it was not comparable to OBS.
Xsplit preset "medium" was not using the same x264 compression features as OBS "medium", that's why in my test, the CPU load was way lower in Xsplit (as was the compression effeciency).

Maybe you can analyze both recordings and check, that they use at least the same ref- and b-frames.
Click to expand...
Well even if that were the case, if I turn my OBS settings to the lowest preset (ultrafast), I get no changes in performance than having it on slow. My bottleneck isn't the processor, like I said before, I'm basically running two completely separate processors because the dies are split.
 
Last edited:
Having the SLI settings (in nvidia's control panel) disabled is not the same as physically removing the second card.
 
Running a game without vertical sync or a frame rate limiter will frequently cause performance issues with OBS because your GPU will be maxed out. Enable vsync or set a reasonable frame rate limit that your GPU can handle without hitting 100% usage. If that's not enough you may also need to turn down some of the video quality options in the game.
Click to expand...
 
Removed the card, got the same exact results as when I had it in and just turned SLI off, huge surprise. So anyway, I'm certain you're missing my point here with your last post. My frame rate being unlimited literally means nothing because I can't get past 90 anyway (my mark).

Your post means the game will cause "performance issues with OBS". Not "it will cause performance issues the game", which is my problem. Don't get them mixed up either by saying "well OBS will make the game have performance issues if these issues are passed to OBS in the first place" which isn't true considering OBS is processor intensive, not GPU. I'm not using NVENC and I turn the preview off (saves about 2% usage on my GPU, maximum).

Anyway, I found a temporary fix which is launching OBS first before any game or processor heavy application. Then launching the game. I'm not sure why this allows me to get back to my original frame rate, but I'll take it.
 
You must log in or register to reply here.
Back
Top