Martin Desruisseaux ha scritto: > Andrea Aime a écrit : >> I also would like to notice another thing. The current HSQL provider >> uses more than 4MB or memory to keep a cache of the tables in the >> DB (that's what the profiler reports, HSQL is the single biggest stable >> memory user in GeoServer). >> I find this wasted memory annoying, since most of the GeoServer >> installations would in fact just use 3-10 CRS, but in an Applet >> that would be a real killer. > > Yes I noticed that too and I agree that this is a problem. This is one > additional reason to abandon HSQL in favor of an other database. If H2 has a > very close API and performs better on memory usage, I'm all for switching to > H2 > at least in short term (before the end of this year - we could open a JIRA > task > for that).
It performs better, I have no data memory usage wise. Anyways, I'm going to send you the zipped epsg-h2 module, but beware about one thing: the h2 jar the pom it's referring is 8 months old and it's quite slow compared to the last one. I get better performance with the last release, not with the one uploaded on the maven repositories. Plus, there is the "read only db" issue I reported here which makes me think h2 is not ready for our intended usage: http://groups.google.com/group/h2-database/browse_frm/thread/ef14b5a50a3d8961 Cheers Andrea ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
