ID:158822
 
Profile results (average time)
Proc Name Self CPU Total CPU Real Time Calls
----------------------- --------- --------- --------- ---------
/mob/verb/Charge 0.009 1.168 7.863 4
/mob/verb/Turbo 0.000 0.074 3.045 8
/obj/bar/proc/update 0.001 0.007 0.007 917
/mob/proc/regen 0.000 0.007 0.007 331
/proc/tileFix 0.006 0.007 0.007 917
/mob/verb/Moves 0.000 0.002 0.561 120
/proc/getTurf 0.000 0.000 0.000 126
/mob/proc/update 0.000 0.000 0.000 471
/atom/movable/Move 0.000 0.000 0.000 881
/obj/dynamic/New 0.000 0.000 0.000 3668
/icon/proc/RscFile 0.000 0.000 0.000 921
/proc/text2dir 0.000 0.000 0.000 477
/mob/verb/blank 0.000 0.000 0.000 184
/obj/ball/Bump 0.000 0.000 0.000 36
/mob/Bump 0.000 0.000 0.000 35
/obj/blur/proc/update 0.000 0.000 0.000 8
/obj/blur2/proc/update 0.000 0.000 0.000 8
/obj/charge/proc/update 0.000 0.000 0.000 4
It means you should have just posted a screen shot of the profiler instead of trying to retype it all?
In response to Falacy (#1)
I don't think he retyped it, there is a button that says Copy on the profiler.
In response to Flame48 (#2)
So there is. Still, a screen shot would be far easier to read. There's also not much point in taking the average, 99% of procs supposedly use 0 each call, then somehow that adds up to 1000 after 10 calls =P
In response to Falacy (#1)
lmfao theres a copy button on it

I didn't even mean to paste all that... What does Self CPU mean, what does total cpu mean and what does realtime mean?
In response to Tubutas (#4)
Tubutas wrote:
What does Self CPU mean, what does total cpu mean and what does realtime mean?

Self CPU is how much that single proc is using. Total CPU includes the CPU from that proc, and all the procs it calls. And real time is how long it actually runs for (in ticks I think).
In response to Falacy (#5)
It also means your Charge() verb is doing something incredibly excessive to be taking so much CPU time for each call.

But the profiler can be wonky, so maybe not.
In response to Garthor (#6)
Garthor wrote:
It also means your Charge() verb is doing something incredibly excessive to be taking so much CPU time for each call.

But the profiler can be wonky, so maybe not.

I have a while statement that should be lasting for a while(no pun intended)(it has sleeps).