Hi,
so I managed to checkout the test scripts from ogc,
and I can now start the cite engine using something like:
engine\bin\test.bat -logdir=target\logs -source=tests\wfs\1.0.0\ets\ctl\wfs.xml
Hum, doing so results in a couple of minutes (maybe more)
or cpu spinning at 100% and then a browser embedded in a
swing frame pops up asking for the usual params.
Holy cow, that seems like a long time to me... what is it
doing? Anything that can be done to speed it up?
Cheers
Andrea
Haha... how did I know that would be your first issue :). I have
complained about this and there does not seem there is much that can be
done. The performance hit comes from using saxon9, as opposed to saxon8,
for some reason it is painfully slow.
I played around with the engine code to try and optimize but failed. You
may have better luck.
Also... I have some batch convenience scripts waiting on the windows vm,
i can commit them.
-Justin
Andrea Aime wrote:
Hi,
so I managed to checkout the test scripts from ogc,
and I can now start the cite engine using something like:
engine\bin\test.bat -logdir=target\logs
-source=tests\wfs\1.0.0\ets\ctl\wfs.xmlHum, doing so results in a couple of minutes (maybe more)
or cpu spinning at 100% and then a browser embedded in a
swing frame pops up asking for the usual params.Holy cow, that seems like a long time to me... what is it
doing? Anything that can be done to speed it up?Cheers
Andrea-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel!DSPAM:4007,47976f43119211961014482!
--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org
Justin Deoliveira ha scritto:
Haha... how did I know that would be your first issue :). I have
complained about this and there does not seem there is much that can be
done. The performance hit comes from using saxon9, as opposed to saxon8,
for some reason it is painfully slow.
Oh sigh... I wonder what kind of computer have those developing the
cite test engine... it's either super fast, so that the problem is
not so visible, or quite slow, so they get an excuse to go grab a
coffee while it starts...
I played around with the engine code to try and optimize but failed. You
may have better luck.
Hmm... why oh why I don't feel lucky today...
Also... I have some batch convenience scripts waiting on the windows vm,
i can commit them.
Ah thank you, just noticed the commit 
Cheers
Andrea