[GRASSLIST:11] Re: Problem with r.contour

[Michael Rensing]

Hamish, thanks for this; it looks like you've got it. I can see the 
memory dissapear towards zero, and then there's a long pause in gui 
response, and r.contour is no more...

I'll have to see if I've got an old disk lying around to add for more 
swap. Or an old wallet with money for more RAM.

If it's still of interest, I have 256M RAM, 512M swap.

At
rows:       8400
cols:       7200
r.contour can complete successfully.

At
rows:       8400
cols:       7680
r.contour gets booted off before completing.

Thanks again,
Michael


Hamish wrote:
>> I've watched the memory use climb while the CPU cycles drop to 1 or 2 
>> percent. Presumably it does into a swap frenzy. The same thing happens
>> whether r.contour finishes successfully or not.
>>     
>
> how big does the memory get? ("M" in top will sort by memory if the
> process slows down) Is that bigger than what you have installed?
>
> Usually a process gets killed when you run out of memory+swap space and
> the OS has to take drastic action to keep the rest of the system from
> crashing.. it kills out the worst memory hog.
>
>
>   
>> How would I measure the size of the areas?
>>     
>
> I was interested in the raster region resolution.
> 'g.region -p' will show number of rows and columns.
>
> v.info will show the number of vector entities involved.
>
>
> Hamish
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/grass-user/attachments/20060311/fad04593/attachment.html