Vala reference counting overhead in high-frequency allocation loops

Vala manages memory through a reference counting mechanism that compiles directly to C. While this avoids the overhead of a garbage collector, the automated generation of reference count increment and decrement operations can introduce performance bottlenecks in performance-critical code paths.

In scenarios where short-lived objects are frequently instantiated and destroyed within a tight loop, the cumulative cost of g_object_ref and similar calls may impact execution speed. While the un keyword can transfer ownership to mitigate unnecessary increments, it does not eliminate the underlying cost for objects that require standard lifecycle management across function boundaries.

What are the measurable performance thresholds where reference counting overhead becomes significant relative manual memory management in Vala? Are there specific compiler flags or patterns that allow the runtime to optimize redundant reference count operations without sacrificing memory safety?