Luigi Ponti wrote:
> > If the latter,
> > you don't see grass using much memory because it is fairly efficent
> > most of the time and doesn't need to- especially the core GIS and
> > raster parts of it. When you consider the amount of RAM+CPU power
> > typically available back when that code was
Hamish wrote:
Luigi Ponti wrote:
As a less-than-two-year old cygwin/GRASS user, I have never seen
virtual memory going over 1 GB while doing intensive computations
with GRASS (e.g., v.surf.idw interpolation).
Have you been getting out-of-memory errors or are you concerned that
you are
Luigi Ponti wrote:
> As a less-than-two-year old cygwin/GRASS user, I have never seen
> virtual memory going over 1 GB while doing intensive computations
> with GRASS (e.g., v.surf.idw interpolation).
Have you been getting out-of-memory errors or are you concerned that
you are not making best use
Glynn Clements wrote:
Luigi Ponti wrote:
As a less-than-two-year old cygwin/GRASS user, I have never seen virtual
memory going over 1 GB while doing intensive computations with GRASS
(e.g., v.surf.idw interpolation). I haven't found much on the topic in
the web so I tried the following to
Luigi Ponti wrote:
> As a less-than-two-year old cygwin/GRASS user, I have never seen virtual
> memory going over 1 GB while doing intensive computations with GRASS
> (e.g., v.surf.idw interpolation). I haven't found much on the topic in
> the web so I tried the following to increase virtual m