Justin Deoliveira a écrit :
Any chance you profiled it to see how much of a performance gain we are
getting now?
I have to admit that no, I didn't profiled it. I just avoided some
elements, like temporary object creation and calls to Math.pow(x,y)
which is know to be slow (in any language; this is not Java fault) but
can be avoided when 'y' is the integer index in a loop. However, I had
to introduce an other pottential bottleneck, which is the synchronized
statement. I will see if I can get ride of it (or at least put a @todo
javadoc tag).
Martin.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
