Before you start, make sure that somewhere in your code you have

#define DEBUG
written.



99% of byond developers are not aware of the tools included with byond for finding out how to catch troublesome procs that are running up all your CPU time! The most important thing that a BYOND coder should do to manage his game is the following:
create a new folder in the same directory as your game's host file and name it cfg. Inside that folder make a new text file called admin.txt

/cfg/admin.txt

Now edit admin.txt and add a line like this

Masterdan role=coder

nothing more to it.
to add more admins

Bustercannon role=eyecandy

save this file like that and any admins you've defined (use their keys) will when joining the server (of course you have to shutdown fully and bring back up the server if you change this file) will be able to do 2 things.

Profile World
Reboot World

Both within Dreamseeker. Now reboot world isnt the point of this tutorial, profile world is. Using Profile world youll get something similar to this CPU Profile of Naruto GOA

Note a few things, /client/Topic is the proc for refreshing the cpu profiler, so the fact that me refreshing the profiler 16 times is our number one lag inducer at 66 people online is a good sign. Topic is also used for other things, but its fairly complicated and if you use it, you should know how it works. Anywho youll be using the Self CPU time mostly for your analysis. Currently our Fire proc uses up the most cpu, 15 calls to fire were used and it is a graphical effect that creates and deletes objects. So nothing is out of the ordinary here. This profile is Total,so its a cumulative effect of roughly 5 minutes of procs running. If you have a proc that has a very high self CPU time and a relatively low amount of calls then you need to worry. Code like that usually is what causes lag spikes which are a games worst enemy. CPU usage isnt a problem when the computer can handle it all, but a quick surge of cpu usage is a problem. You can remedy alot of heavy workload tasks by slipping calls to sleep(-1) and using sleep(positivenumber) more often. Look up sleep for more on that in the DM references. Anyway dont pay much thought to realtime as its the literal time spent on a proc which really doesnt mean anything to you. Total cpu time tells you the cpu used up not just by the proc but by the proc and every other proc IT calls. So sometimes when you have a proc with a very high total cpu but a high amount of calls you want to look for a proc thats got a high total cpu time to find out what has been calling the offending proc so darn often. Also the average button can be used to find the cpu used on 1 iteration of a proc, useful when weeding out lag spikes as a proc that uses up 1.00 of self cpu time on average will really beat the crap out of the server.

Cheers!

PS: One note i should make, when contesting wether or not 2 games are from the same source, submitting both cpu profiles to an impartial judge is a good way of determining if the code is in fact the same. However the thin disguise of changing the names of procs would make this more difficult to compare, still you can read a great deal into how a games code is done simply by looking at this. a Querky detail thats similar between 2 sources such as maybe GOA's AOExk2 [which is Dan gibberish for my AreaOfEffect x(dont effect the caster) k2(specified range and a sequel to the regular AOExk proc) is definete proof of ripping! GOA isnt afraid of its code of course, so our cpu profile is publically posted now :D