Re: Linux locks up when handling large data sets

David T. Lewis wrote:
> 
> 
> 
> You are probably just growing your image to the point where the operating
> system starts swapping. The image will appear to be unresponsive, but if
> you interrupt it with <alt>period, it will eventually wake up and return
> control to you.
> 

David, my image doesn't respond to <alt>period, although it is still using
processor. It didn't sort itself out when left overnight.


David T. Lewis wrote:
> 
> The Unix VM automatically allocates memory from the operating system
> as the Squeak object memory grows. This has the nice property of making
> the image just as big as it needs to be without you worrying about it,
> but it also means that if you write code that allocates far more memory
> that is physically available, the operating system is going to start
> thrashing to the point where Squeak becomes unusable. It will not really
> be frozen though; if you are patient enough you can still save the image,
> install more memory on your computer, and restart it ;-)
> 
> johnps11@xxxxxxxxxxx gave so good tips on how to control VM memory
> allocation for the Unix VM.
> 
> 

Yes, using John's tips I can handle much larger data sets; I posted the
results to his post.


David T. Lewis wrote:
> 
> I have also found that large images that I make on a Linux box
> may refuse to load on Windows, with the Windows VM apparently
> unable to allocate enough memory (even though plenty of memory
> is available). I'm afraid that I never bothered to figure out
> why (possibly error or ignorance on my part) but I mention it
> so you won't be surprised if you try to show off your large
> data sets on someone else's Windows laptop.
> 
> Dave
> 
> 

Interesting, I might try this too to see what happens.

Thanks for your reply,    Stan

-- 
View this message in context: 
http://www.nabble.com/Linux-locks-up-when-handling-large-data-sets-tp17027341p17039414.html
Sent from the Squeak - Beginners mailing list archive at Nabble.com.