[mkgmap-dev] Memory limits for mkgmap and splitter
From Chris Miller chris.miller at kbcfp.com on Wed Aug 5 16:01:59 BST 2009
> thanks a lot for new splitter beta release. I tried your version with > a small region (Bayern in Germany). Max nodes 800.000, 12 tiles: > > old splitter: 310 MB RAM > new splitter: 240 MB RAM > old splitter: 370 sec > new splitter: 470 sec Hmm, I'm surprised the new version is taking longer actually. I didn't benchmark my most recent changes so perhaps I've done something silly. It should be the same speed or faster than the old. Thanks for the statistics, I'll take a look and see what I can do to get it back up to speed. > old splitter: problem with 31 relations in more than 4 tiles > new splitter: no problem That's in line with what I'd expect given my latest change. > old splitter: problem with 2 ways in more than 4 tiles > new splitter: problem with 2 ways in more than 4 tiles Again, this is in line with what I'd expect, I haven't done anything to solve this so far. Fixing ways that span more than 4 tiles is tricky unfortunately without hurting both memory usage and performance. I don't think I'll be able to address this limitation in the short term but I'm certainly aware it's a problem and have some ideas on how to tackle it down the line. Thanks for the feedback, much appreciated. Chris
- Previous message: [mkgmap-dev] Memory limits for mkgmap and splitter
- Next message: [mkgmap-dev] Memory limits for mkgmap and splitter
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list