[OpenMap Users] Debug takes a lot of cpu

From: Tore Halset <halset_at_pvv.ntnu.no>
Date: Wed, 7 Feb 2007 11:06:10 +0100


I am doing some profiling of my app here and it looks like Debug is
using way too much cpu. Ofthen used methods like Length.roRadians and
LLXY.forward all calls Debug.debugging that does a

I do not want and openmap debug output, but changing Debug.On to
false is not possible as it is static final.

Here you see a screenshot from jprofiler. This is the CPU Hotspot
view. Projection and drawing are taking most of the cpu, but I think
Debug is taking way too much.

Is there a master plan for logging in openmap? Like switching to a
more common logging solution. Or should I hack my own Debug to set
Debug.On to false?

  - Tore.

[To unsubscribe to this list send an email to "majdart_at_bbn.com"
with the following text in the BODY of the message "unsubscribe openmap-users"]
Received on Wed Feb 07 2007 - 05:11:22 EST

This archive was generated by hypermail 2.3.0 : Tue Mar 28 2017 - 23:25:08 EDT