Hi Tore,
Thanks for the profiling information. It looks like those three
com.bbn.openmap.proj methods are the main hotspots for Debug, so I
can take a look at that to reduce the load on Debug for the next
release.
The master plan for OpenMap logging is to move to the logging
mechanism in the jdk. For all of the new code I've written for
OpenMap I've replaced Debug with Logger, and I'll be re-factoring the
other classes for the 4.7 release.
I'm not sure why the Debug.On flag is final, it shouldn't be.
- Don
On Feb 7, 2007, at 5:06 AM, Tore Halset wrote:
> Hello.
>
> 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
> Hashtable.containsKey.
>
> 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.
> http://www.pvv.ntnu.no/~halset/tmp/20070207-openmap-jprofiler.png
>
> 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"]
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Don Dietrick, dietrick_at_bbn.com
BBN Technologies, Cambridge, MA
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
--
[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 - 08:16:49 EST
