the profiler is not really meant to be used in a public server - it needs a lot of resources.
the best, and quickest way is to add the profiler in your (local) server.cfg, let it profile the gamemode + relevant filterscripts, and let it run for some time.
if any function proves to be cpu-hungry, it will show in the profile output.
oh, i forgot to mention that you need to recompile all scripts, in order to get the symbolic information (like callback names/addresses etc) being written into the .amx file.
its a good idea to start profiling the gamemode only, then add the filterscripts.
edit: heres a short run of my gamemode:
Код:
Type Name Calls Self Time Total Time
public OnGameModeInit 1 18.91 18.91
public main 1 0.00 0.00
public TimerServicesM 69 0.27 0.27
public ZoneXYTimer 70 3.61 3.61
public TimerServices4 1335 2.05 2.05
public ScrollTimer 690 64.89 64.89
public ZoneTimer 46 2.19 2.19
public TimerLotto 66 0.40 0.40
public TimerSync 90 0.43 0.43
public TimerServices3 140 1.17 1.17
public TimerServices2 35 6.05 6.05
public LevelDecreaseTimer 2 0.00 0.00
public TimerServices1 1 0.00 0.00
public OnGameModeExit 1 0.01 0.01
as you can see, my "ScrollTimer" seems to eat a lot of cpu - its one relict i wanted to get rid off, and never optimized it... the "total time" proves it ><