A year ago when the CSS extension was a community module,
I posted that when moving from GeoServer 2.2 to 2.3 it had become much slower saving and auto-checking CSS.
At the time David Winslow queried if it was memory related and he also said that he had some performance improvements that he had been sitting on.
Trying now on GeoServer 2.5 with multiple Xmx (1024M/2048M)and MaxPermSize (128m/256m) setting,
I still find that the performance is still very poor and makes the extension problematic to use and prevents me upgrading.
Please, please tell me that something can be done about this.
Many thanks,
Simon Hartley
P.S.
When profiling, the method that takes most time (85s) is: scala.collection.immutable.StringLike#toDouble.
When I took up the implementation, it delegates to java.lang.Double.parseDouble.
Second is scala.runtime.ScalaRunTime#hash (11s).
Third is scala.collection.LinearSeqOptimized#sameElements (2s)
Fourth is org.geoscript.geocss.DataSelector#filterOpt (1.4s)
If I connect later while it’s still going:
second is scala.collection.AbstractIterator#forAll and third is scala.collection.AbstractIterator#exists;
scala.collection.immutable.StringLike#toDouble has hit 1800s (30 minutes) by this point.
.
*** This communication has been sent from World Fuel Services
Corporation or its subsidiaries or its affiliates for the intended recipient
only and may contain proprietary, confidential or privileged information.
If you are not the intended recipient, any review, disclosure, copying,
use, or distribution of the information included in this communication
and any attachments is strictly prohibited. If you have received this
communication in error, please notify us immediately by replying to this
communication and delete the communication, including any
attachments, from your computer. Electronic communications sent to or
from World Fuel Services Corporation or its subsidiaries or its affiliates
may be monitored for quality assurance and compliance purposes.***