amx_debug / JIT performance

Syturi0 · **Author**

Quote:

// Plugin Debug mode
// 0 - No debugging (garbage line numbers)
// 1 - Plugins with "debug" option in plugins.ini are put into debug mode
// 2 - All plugins are put in debug mode
// Note - debug mode will affect JIT performance
amx_debug 1

What does "JIT" stands for?
Is it bad if i let amx_debug always on value 2?

fysiks · *Last edited by fysiks; 05-22-2017 at 01:00.*

"Just in Time"

Any time that you add debugging you add overhead. So, if you don't have a specific reason to have debugging enabled, then don't enable it.

Syturi0 · *Last edited by Syturi0; 05-22-2017 at 01:00.*

Quote:

Originally Posted by fysiks

Just think of that line as.

How much will it affect? Thats what iam trying to figure out. Do i have to worry about leaving it on all the time?

fysiks · *Last edited by fysiks; 05-22-2017 at 01:12.*

Leave it on and see what happens. Performance has too many variables to know how much just one of them will affect it and how much. If you have a million plugins then it will affect it more than if you had 2 plugins.

Syturi0 · 05-22-2017 , 01:08 Re: amx_debug / JIT performance

I only have 1 plugin, but its a huge one with 11k+ lines.
I have been using it on value "2" for ever and never noticed anything negative.
I also tried setting it to value "0", no difference... ping / server FPS, everything stays the same.

fysiks · 05-22-2017 , 01:14 Re: amx_debug / JIT performance

For reference: https://en.wikipedia.org/wiki/Just-in-time_compilation