[osmosis-dev] nodes column in way table and way_nodes table

[Brett Henderson]

Wow, okay.  Perhaps the planet is just too big now.  I've never had enough
RAM to run it properly so don't have any numbers.  I've always had to use
nodeLocationStoreType=TempFile which is still faster than building
linestrings in the database itself.  It may also be worth experimenting
with nodeLocationStoreType=CompactTempFile which is more efficient for
small datasets.  I haven't done testing to determine the size of dataset at
which TempFile becomes better than CompactTempFile.

On 27 December 2011 19:21, Michel Seuthe <m.seuthe at googlemail.com> wrote:

> I did. 64-bit cmd.exe, 64-bit JVM and -Xmx 16000. It uses all the
> physically available memory (nearly 16GB) and throws the exception when
> that limit is reached.
>
>
> 2011/12/26 Brett Henderson <brett at bretth.com>
>
>> On 26 December 2011 01:43, Michel Seuthe <m.seuthe at googlemail.com> wrote:
>>
>>> Ya, I used a similar statement. It took a few hours to build the
>>> linestrings for germany.
>>> I tried to use osmosis to build the geometries, but it always threw
>>> SystemOutOfMemory Exception when the linestring column was added to ways
>>> table. The box osmosis was running on got 16GB RAM and I used InMemory
>>> option.
>>>
>>
>> Did you specify the -Xmx option to java?  Were you using a 64-bit JVM?
>> Java by default will automatically set a maximum available memory size
>> which is fairly small compared to overall system RAM.
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/osmosis-dev/attachments/20111227/439e83d8/attachment.html>