How to Enable and Use the MicroTiming Logger to Profile Lag Spikes

Turning the logger on

The microTiming logger is a profiling tool that records how long individual parts of the game tick take, so you can find what is actually causing lag instead of guessing. Open your in-game Carpet settings (the /carpet command or the settings GUI) and look for the microTiming option. Enable it, then let the game run while the lag happens. The logger collects timing data passively, so you do not need to do anything special during the capture window.

Reading the output

Once you have captured a representative period, use the command that dumps the timing report to chat or to a log file. The report breaks the tick down into named sections and shows how much time each consumed. Sort your attention by the biggest contributors first — a single section dominating the total is your culprit. Common offenders are entity ticking, block entity ticking, and chunk-related work.

Acting on the results

If entity ticking dominates, look for mob farms or large clusters of entities and reduce them. If block entities dominate, check for dense storage or machine setups. Re-run the logger after each change to confirm the section shrank. Because the mod does not alter vanilla behavior by default, enabling this logger will not change your world's gameplay — it only measures. Disable it when finished, since profiling itself carries a small overhead.