My first impression is 2.5 hours is a very long time but it depends on ...
- What do you build ?
- What do you use (world bounds, world coastlines) ?
- What are your hardware resources (number of cores, ram, ...) ?
- Which OS are you using ?
- ...
A finding from yesterday: Using the world
On Wed, Jan 04, toc-rox wrote:
My first impression is 2.5 hours is a very long time but it depends on ...
- What do you build ?
- What do you use (world bounds, world coastlines) ?
- What are your hardware resources (number of cores, ram, ...) ?
- Which OS are you using ?
- ...
I don't
My first impression is 2.5 hours is a very long time but it depends on ...
- What do you build ?
- What do you use (world bounds, world coastlines) ?
- What are your hardware resources (number of cores, ram, ...) ?
- Which OS are you using ?
- ...
A finding from yesterday: Using the world
That sounds great!!
Thanks for the feedback :-)
WanMil
Hi,
I only wanted to give some feedback about the speedup patches:
The time to build my maps was reduced by one
hour from 3.5 to 2.5 hours. Very impressive.
Thorsten
___
mkgmap-dev
Hi,
great job!!!
I'm saving now about 13 minutes (-17%) of mkgmap-runtime. In detail:
Germany: 19:17 (2154: 24:52) -22%
Turkey: 00:58 (2154: 01:04) -09%
Scandinavia: 08:58 (2154: 10:33) -15%
BeNeLux: 09:27 (2154: 11:00) -14%
Alps: 15:03 (2154: 18:30) -19%
GreatBritain:
