[osmosis-dev] [PATCH] Allow user to set buffer sizes instead of hardcoding them in --merge and other tasks

Igor Podolskiy igor.podolskiy at vwi-stuttgart.de
Fri Jun 24 12:53:24 BST 2011


Hi @osmosis-dev,

during my recent work I noticed that --merge, --merge-change, 
--apply-change, --derive-change and --append-change use input buffers 
(DataPostbox) but don't allow me to set the buffer size, hardcoding it 
instead to very low values (10 or 20). I was able to achieve serious 
performance improvements for big data sets (up to 3x faster with 
apply-change) by modifying those tasks to accept an additional command 
line parameter and setting the input buffer size to something more 
appropriate for my hardware, like 10000.

The attached patch contains my modifications. It's mostly trivial, as 
the input buffer size is already a parameter and I only needed to add 
argument handling in the task factory.

This change is fully backwards compatible with respect to the behavior 
or the user interface of the tasks (I believe at least).

Needless to say, if the patch gets applied, I volunteer to update the 
wiki pages :)

Greetings from Stuttgart
Igor
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: buffer-size.patch
URL: <http://lists.openstreetmap.org/pipermail/osmosis-dev/attachments/20110624/5308e5c5/attachment.ksh>


More information about the osmosis-dev mailing list