
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.
I've just run another benchmark against united_kingdom.osm.bz2 (170MB compressed, 2.1GB uncompressed, 9,500,000 nodes). When running against the compressed file I get the following results: old splitter: 590 sec new splitter: 536 sec This is more in line with what I'd expect. Almost all the time savings come from the first stage (calculating the areas.list file), while the second stage takes almost identical times in both splitters. Can you please tell me exactly what parameters you used to run both the old and the new splitters to get your results? Would it be possible to get hold of the osm file you used to run your test against? I'd be interested in replicating the poor performance so I can try to fix it. Regards, Chris