Quick Answer

The CPU is clear enough, but the RTX model is missing, so the useful answer is conditional: a Ryzen 7 9700X is strong for this game and the named GPU must be confirmed before a final bottleneck verdict. For SA buyers, do not spend R30,000-R55,000 on a GPU tier unless your monitor, resolution, and game list can use it in Dragon Ball Sparking Zero.

What The Bottleneck Looks Like

A CPU limit appears when GPU utilisation drops while frame time spikes and lowering graphics settings does not improve the result. A GPU limit appears when utilisation stays high and reducing resolution, ray tracing, or texture load improves fps. 60 fps is the usual target for cinematic play, while 120 fps needs both GPU detail control and a high-refresh screen.

SA Build Context

Pair premium GPUs with the right platform support: 32 GB DDR5, a quality 750-1000 W PSU depending on GPU tier, and a board such as MSI B650 Tomahawk, ASUS TUF B760-Plus, or a matching Z790/Z890 option. Broad local planning bands are R4,000-R14,000 for the CPU tier and R6,000-R55,000 for the GPU tier, depending on model.

Settings That Give A Clean Test

Use the same scene, same preset, and the same frame cap for each run. Check 1% lows, not only average fps. If the game feels uneven, try a sensible cap such as 120 fps, 144 fps, or 165 fps before replacing working parts.

FAQ

Is the Ryzen 7 9700X strong enough for the RTX graphics card?

Yes for most gaming targets. The exception is very high-refresh 1080p where even strong CPUs can become the ceiling before the graphics card is fully loaded.

Should I upgrade the CPU or GPU first?

Upgrade the GPU first when utilisation is high and visual settings drive the fps drop. Upgrade the CPU platform only when frame pacing stays poor after lowering GPU-heavy settings.

What monitor makes this pairing sensible?

For 1440p, use a display that matches the spend: 144 Hz or 165 Hz for balanced play, and 240 Hz only if your games can sustain it. A weak 60 Hz screen wastes much of a premium build.

{{TipBox title:"Test Tip" , Log average fps, 1% lows, GPU use, and frame cap in the same scene; the limiting part becomes obvious when the numbers repeat. }