#2045: r.to.vect: use less memory
--------------------------+-------------------------
Reporter: mlennert | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 7.0.5
Component: Raster | Version: svn-trunk
Resolution: | Keywords: r.to.vect
CPU: Unspecified | Platform: Unspecified
--------------------------+-------------------------
Comment (by mmetz):
Replying to [comment:16 mlennert]:
> Replying to [comment:15 mlennert]:
> >
> > I did use GRASS_VECTOR_LOWMEM=1, but the process was stopped. No
explicit memory error, but AFAIK such stopping of a process happens in
case of memory errors:
> >
> >
> > {{{
> > Enregistrement des primitives ...
> > 63282475 primitives registered
> > 397657832 vertices registered
> > Construction des surfaces ...
> > Processus arrêté
> >
> > real 106m12.306s
> > user 28m2.664s
> > sys 68m42.260s
> > }}}
> >
> > Next try will be to use v.build on the vector created by r.to.vect
-b...
>
>
>
> {{{
> > export GRASS_VECTOR_LOWMEM=1
> > time v.build seg_full
> Construction de la topologie pour la carte vectorielle
> <seg_full@rtovecttest>...
> Enregistrement des primitives ...
> 63282475 primitives registered
> 397657832 vertices registered
> Construction des surfaces ...
> Processus arrêté
>
> real 84m57.309s
> user 19m8.872s
> sys 54m37.868s
> }}}
Strange. Topology building should be much slower with GRASS_VECTOR_LOWMEM,
therefore I would expect v.build with GRASS_VECTOR_LOWMEM to fail later,
not earlier. Can you provide data and commands for testing?
>
> 
>
> I, therefore, do not have any means to vectorize this file directly in
one piece on my computer. Memory usage goes up steadily through v.build.
>
> I'll try r.to.vect.tiled.
This should also fail if you want r.to.vect.tiled to patch the tiles
together.
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/2045#comment:18>
GRASS GIS <https://grass.osgeo.org>