Addon hooks Lag Finder

This addon finds the laggiest hooks and displays them in console. It is not magic, read description to learn how to use it!

Available on GitHub: Addon hooks Lag Finder

The reports display laggy hook names, performance impact, file location and matching Workshop addon.

Proceeding with the test to identify a lag that is not observable will not help. Locating a lag implies that a lag is occurring.

Currently, inspected hooks are from: GM, hook, net, usermessage, timer, ENT, SWEP and the main scene rendering. This addon ignores lags from VGUI and lags that do not involve Lua.

As a golden rule, avoid modifying Lua files during the test, in order to prevent restoring old functions and to prevent ignoring added / reloaded functions.

GM, ENT and SWEP functions added / modified / reloaded during the test are ignored and an old version will be restored at the end of the test. Hooks / callbacks added / modified / reloaded without the provided function during the test will be ignored.

The Addon hooks Conflict Finder is required in order to identify Workshop addons. The Addon hooks Conflict Finder is the base of this addon. See its description.

Usage

These commands must be entered in console. The command finishing with "sv" is for a serverside test, only for superadmins. The command finishing with "cl" is for a clientside test.

• To start a simple test:

find_laggy_hooks_sv
find_laggy_hooks_cl

• To stop a simple test:

find_laggy_hooks_sv 0
find_laggy_hooks_cl 0

• Full syntax:

find_laggy_hooks_sv [ReportInterval=30 or 0] [TopCount=16 or RatioThreshold]
find_laggy_hooks_cl [ReportInterval=30 or 0] [TopCount=16 or RatioThreshold]

ReportInterval - How many seconds between reports, small values recommended TopCount - How many hooks to display on each report RatioThreshold - Display all hooks above the given impact threshold, example: 0.1 means 10%

The more ReportInterval is high, the less you will see one-time lags on top of the list. This is due to the Impact which is not affected by the unreliable Max time.

Columns

Identifier: The type and the name of the hook Impact: Calculated impact on framerate Executions: Number of executions of the hook during last capture period Mean time per frame: Mean execution time per frame over last capture period Max time: Maximum execution time of the hook

Known bugs

• The time measurement often goes wrong, causing Max time to have a crazy high value.

See also

DBugR, by oubliette32 LagDetector, by Buzzkill FProfiler, by FPtje

Good luck!