Hi Bernd, I got similar results for a larger set on my PC. I think the large value is no improvement, and if I got that right it means that some MB can't be used for something else. I assume your Bonn extract will not even contain 1000003 different strings.
Gerd > From: [email protected] > To: [email protected] > Date: Thu, 8 May 2014 18:28:22 +0200 > Subject: Re: [mkgmap-dev] Java tuning hint > > Am Donnerstag, 8. Mai 2014, 17:33:22 schrieb Gerd Petermann: > > Hello Gerd > > I've made three tests with my bonn extract > > without -XX:StringTableSize > Time started: Thu May 08 17:57:43 CEST 2014 > Time finished: Thu May 08 18:04:54 CEST 2014 > Total time taken: 430804ms > > with -XX:StringTableSize=100003 > Time started: Thu May 08 18:07:33 CEST 2014 > Time finished: Thu May 08 18:14:20 CEST 2014 > Total time taken: 406425ms > > with -XX:StringTableSize=1000003 > time started: Thu May 08 18:16:20 CEST 2014 > Time finished: Thu May 08 18:23:06 CEST 2014 > Total time taken: 405556ms > > This are tests on my small laptop with 3.6 GB RAM with 64bit Linux > > Bernd > > > I tried both, and the smaller values seemed to work better for mkgmap. > > I guess it depends on the input files what value is best, but at least > > the default 1009 doesn't work well, so any much higher prime value should > > help. > > _______________________________________________ > mkgmap-dev mailing list > [email protected] > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list [email protected] http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
