Profilers in eqemu
 

Looking through the source I see a lot of calls to _ZP and such which got me digging for answers. I discovered a system of profilers built into eqemu. Rather than spend a bunch of time digging through the source for answers, and since I couldn't find any applicable forum posts already existing, I figured I'd ask you all about these profilers.


First off, these are just profilers for measuring performance, right? I saw they involved a lot of timer code so I'd assume so.

Is any logic in real time affected by these profilers to say balance performance? Or are they just used to diagnose and solve performance issues?

By default is something such as the zone profiler enabled and active, or must you setup a certain debug level or some other flag for its functions to actually process? What are my options here? I didn't see anything in the limited debug documentation.


If someone could just summarize the functionality of profilers in eqemu it would make it a lot easier for me and many others I'm sure. Thanks for any help.

It's pretty limited as it hasn't been maintained in the time I've been here. Honestly I was recently thinking about taking it out.

I think they should be removed as well. The profiler code should stay in a toolkit library which is optional IMO. The information they produce is probably only interesting to a handful of people and only meaningful/useful to fewer.