gc.buffer (not a Rust ConVar)
Some Rust performance guides still set gc.buffer, but current Rust servers do not list it. What the gc namespace has and what to do with old configs.
Last updated Verified on Rust build 25582902, 2026-09-28
- Listed on build 25582902
- No. find . does not list it and reading it over RCON returns nothing, so there is nothing to set.
gc.buffer still shows up in Rust server performance advice, described as a garbage collection setting, sometimes with a size in megabytes such as 256 or 512. On current builds it is not a setting the server knows.
What the server says
On our test server (Rust build 25582902, September 2026):
find .lists every console variable and command, and there is nogc.bufferamong them.- Sending
gc.bufferover RCON returns nothing, the same as any name the server does not recognise.
The gc namespace on this build contains exactly these entries:
| Name | Value | Help text (shortened) |
|---|---|---|
gc.enabled | True | (Generated) When enabled, this system is globally active; disable to deactivate the system for the current session |
gc.incremental_enabled | True | (Generated) Read-only: reports whether Unity incremental garbage collection is enabled for this runtime; cannot be changed at runtime |
gc.incremental_milliseconds | 3 | (Generated) Time slice in milliseconds allocated to incremental GC per frame |
gc.collect | command | (Generated) Triggers an immediate full managed garbage collection pass |
gc.alloc | command | (Generated) Allocates a byte array of the given size as a GC pressure test |
gc.unload | command | (Generated) Calls Resources.UnloadUnusedAssets() to unload assets no longer referenced by any object |
None of them is a buffer size, so there is no drop-in replacement to put in its place.
What to do with an old config
Remove gc.buffer from your startup command or server.cfg, wherever you put it. On our test server, names the server does not know on the command line are reported at every start with a line such as Command 'batchmode' not found, so expect a similar line for gc.buffer. There is no setting behind the name for it to change, and the extra line only makes the startup log noisier.
We do not know which Rust update removed it. If you are chasing memory or stutter problems, measure first: serverinfo over RCON reports Memory and Framerate. If the server is being killed for running out of memory, see Rust server killed out of memory.
Related ConVars
- gc.incremental_milliseconds(Generated) Time slice in milliseconds allocated to incremental GC per frame; lower values reduce GC stutter but spread collection over more frames
- gc.incremental_enabled(Generated) Read-only: reports whether Unity incremental garbage collection is enabled for this runtime; cannot be changed at runtime
- gc.collect(Generated) Triggers an immediate full managed garbage collection pass; useful after large allocations for memory profiling
Skip the manual work: install the Panelra agent
Wipes, updates, restarts, plugins and crash alerts for your Rust servers, from one dashboard. One install command on your Linux host, no inbound ports for the agent.
Free during the open beta. Pricing will be announced before the beta ends.