Hi Ruediger, 8000 threads! That's impressive :-)
Unfortunately there's not much you can do about it. Osmosis will use one thread per xml reader, and one thread per merge task. It's probably possible to develop a more efficient implementation but your use case sounds fairly unusual. If it won't run properly with 8000 threads you could try running Osmosis in several passes by combining smaller sets together then combining merged files into larger merged files. Cheers, Brett On Fri, Sep 16, 2011 at 12:17 AM, Gubler, Ruediger <[email protected]>wrote: > Oh no, > > I found the error: > > for(String fileStr : subFiles) > { > argsList.add("--fast-read-xml " + new File(dir, fileStr).canonicalPath) > count++ > } > for(int ii = 1; ii < count; ii++) > { > argsList.add("--merge") > } > argsList.add("--wx " + new File(localDirectory, "tmp/osm/merged.osm")) > > > must be > > > for (String fileStr: subFiles) > { > argsList.add("--fast-read-xml") > argsList.add(new File(dir, fileStr).canonicalPath) > count++ > } > for (int ii = 1; ii < count; ii++) > { > argsList.add("--merge") > } > argsList.add("--wx") > argsList.add(new File(localDirectory, "tmp/osm/merged.osm").canonicalPath) > > > The arguments must different entries not "--fast-read-xml c:\...." but > "--fast-read-xml" "c:\...." > > > Now it works but osmosis is using over 8000 threads for 1904 *.osm files to > merge ?! > > > > Yours Rüdiger > > > _______________________________________________ > osmosis-dev mailing list > [email protected] > http://lists.openstreetmap.org/listinfo/osmosis-dev >
_______________________________________________ osmosis-dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/osmosis-dev
