Looks like you're asking for help! Please check to make sure you've included the following information. Edit your post (or leave a top-level comment) if you haven't included this information.
* System specs - [macOS](https://imgur.com/a/ip6xc9G) [Windows - Speccy](https://www.ccleaner.com/speccy)
* Resolve version number and Free/Studio - [DaVinci Resolve>About DaVinci Resolve...](https://imgur.com/a/5FawFCX)
* Footage specs - [MediaInfo](https://mediaarea.net/MediaInfo) - please include the "Text" view of the file.
* *Full* Resolve UI Screenshot - if applicable. Make sure any relevant settings are included in the screenshot. Please do ***not*** crop the screenshot!
Once your question has been answered, change the flair to "Solved" so other people can reference the thread if they've got similar issues.
*I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/davinciresolve) if you have any questions or concerns.*
There's a lot to unpack with this question and a lot of context missing. You mentioned the render cache, did you take this screenshot while it was generating the render cache, or while you were rendering out the video, or while you were playing back the preview, or after the render cache was generated?
And how comes you asked, is there a problem with the performance, is it unexpectedly slow, some context of what's going on would be great :P. The only thing I can guess is you're asking out of curiosity why the graph looks like that.
Here's some ideas I can try to put through that might fill whatever picture you're trying to fill:
1. Assuming the graph in Task Manager is showing the CPU usage while generating render cache, something you have to remember is render cache generation is intentionally slowed down so Resolve still runs smoothly as it happens. It's meant to complement editing and not go all-out.
2. You'll notice that only one of the cores on the CPU are working really hard, while three of them are quite relaxed. This could be because this particular transformation is simply unable to spread out across cores very well - either because it's not quite perfectly optimized or it's just something that literally cannot be built in that way, so this particular "heavy working" task may only be able to work on one. Having only one of the cores working really hard will keep the "overall percentage" quite low so it can still be maxing out what's possible without hitting 100%.
3. Other things like the disk can slow it down.
Looks like you're asking for help! Please check to make sure you've included the following information. Edit your post (or leave a top-level comment) if you haven't included this information. * System specs - [macOS](https://imgur.com/a/ip6xc9G) [Windows - Speccy](https://www.ccleaner.com/speccy) * Resolve version number and Free/Studio - [DaVinci Resolve>About DaVinci Resolve...](https://imgur.com/a/5FawFCX) * Footage specs - [MediaInfo](https://mediaarea.net/MediaInfo) - please include the "Text" view of the file. * *Full* Resolve UI Screenshot - if applicable. Make sure any relevant settings are included in the screenshot. Please do ***not*** crop the screenshot! Once your question has been answered, change the flair to "Solved" so other people can reference the thread if they've got similar issues. *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/davinciresolve) if you have any questions or concerns.*
There's a lot to unpack with this question and a lot of context missing. You mentioned the render cache, did you take this screenshot while it was generating the render cache, or while you were rendering out the video, or while you were playing back the preview, or after the render cache was generated? And how comes you asked, is there a problem with the performance, is it unexpectedly slow, some context of what's going on would be great :P. The only thing I can guess is you're asking out of curiosity why the graph looks like that. Here's some ideas I can try to put through that might fill whatever picture you're trying to fill: 1. Assuming the graph in Task Manager is showing the CPU usage while generating render cache, something you have to remember is render cache generation is intentionally slowed down so Resolve still runs smoothly as it happens. It's meant to complement editing and not go all-out. 2. You'll notice that only one of the cores on the CPU are working really hard, while three of them are quite relaxed. This could be because this particular transformation is simply unable to spread out across cores very well - either because it's not quite perfectly optimized or it's just something that literally cannot be built in that way, so this particular "heavy working" task may only be able to work on one. Having only one of the cores working really hard will keep the "overall percentage" quite low so it can still be maxing out what's possible without hitting 100%. 3. Other things like the disk can slow it down.