I'm usually able to run most test levels at a solid 100+ fps with default graphics settings. Big maps and higher settings can bring it down to 60. Things I'm working on rarely push the game to the limit while I'm working because I'm not working on the high fidelity visuals. My workstation is fairly standard for our technical design and engineering teams.

When our workstations are in the office, they're often used for distributed build systems like Incredibuild, SN Systems, Jenkins, and the like. This allows us to compile code faster because we can have multiple idle machines split the work up across them. I'm a fully remote worker so my workstation doesn't participate in the distributed build system.

In my case, the situation that pushes my workstation to its limits tends to be when I'm building and compiling assets. I've seen both my CPU and my memory footprint go up to 98% with noticeable slowdown and choppiness doing anything else on the machine. Processing assets and building levels tends to eat as many resources as I'm willing to give.
[Join us on Discord] and/or [Support us on Patreon]
Got a burning question you want answered?
- Short questions: Ask a Game Dev on Twitter
- Short questions: Ask a Game Dev on BlueSky
- Long questions: Ask a Game Dev on Tumblr
- Frequent Questions: The FAQ