[GRASS-dev] v.in.ogr Killed by Linux for saturating RAM+SWAP

GRASS GRASS developer
1

Hi devs,
I am trying to import a vector and it gets killed. Is there a direct way to let it not use the whole RAM+SWAP or should I get a bigger RAM system to do the manipulation ?
Thanks,
Yann

Importing 6146401 features (OGR layer )…
100%

···

Dr. Yann Chemin
+33 7 83 85 5234
JRC, Ispra, IT

2

Hi Yann,

Did you try:

GRASS_VECTOR_LOWMEM

Environment variable?

See:

https://grass.osgeo.org/grass76/manuals/variables.html

Cheers

Stefan

···

Hi devs,

I am trying to import a vector and it gets killed. Is there a direct way to let it not use the whole RAM+SWAP or should I get a bigger RAM system to do the manipulation ?

Thanks,

Yann

Importing 6146401 features (OGR layer )…
100%

Registering primitives…

Cleaning polygons

Breaking polygons…
Breaking polygons (pass 1: select break points)…
100%
Breaking polygons (pass 2: break at selected points)…
Killed

Dr. Yann Chemin

+33 7 83 85 5234

JRC, Ispra, IT

3

Answering to my own question.

I can increase the SWAP size on a running Linux by:

sudo swapoff -a
sudo dd if=/dev/zero of=/swapfile bs=1G count=8

8+0 records in
8+0 records out
8589934592 bytes (8.6 GB, 8.0 GiB) copied, 12.7623 s, 673 MB/s
sudo mkswap /swapfile
Setting up swapspace version 1, size = 8 GiB (8589930496 bytes)
no label, UUID=xxxxxxxxx
sudo swapon /swapfile
grep SwapTotal /proc/meminfo

···

Dr. Yann Chemin
+33 7 83 85 5234
JRC, Ispra, IT