TYPES OF FUNCTIONS:

1. CPU NATIVE FUNCTIONS / PROCESSES

2. GPU NATIVE RENDER FUNCTIONS / PROCESSES

(WHICH IS DONE BY BEVY)

Notes: External libraries also degrade sometimes in performance. We also need to have that in account.

CRATE: processing_render

TL;DR: processing_render is mostly CPU-heavy in the parts that generate and prepare render data: tessellation, mesh generation, geometry mutation, shader/material setup, command flushing, and buffer/image conversion. These CPU-side generators are the most likely areas contributors will modify, so V1 should focus on deterministic CPU benchmarks for those hot paths.

For GPU benchmarking, we should measure the complete rendering pipeline rather than isolated snippets, because actual GPU work is mostly executed inside Bevy/wgpu. A full render benchmark harness can be added in V2 for frame time, GPU compute dispatch, readback, particles, and end-to-end scene rendering.