Here's my two-penn'orth, which will have everyone shaking their heads in pity...
Why don't you post the code which blows up for you, Dieter? Or maybe a simplified sample which reproduces the problem. Then I can try it on my new g-wiz iMac -- I haven't seen an out-of-memory yet. That's because as a coder I'm a timid old dinosaur and haven't got used to 4MB of RAM, let alone 4GB. But the Mac may have some VM tricks up its sleeve: those Apple folk have been fitting quarts into pint pots since 1985. Perhaps I'll be treated to the sight of 603GB of disk filling up before my eyes with (presumably) meaningful calculations. :) Bill is right though -- the iMac under Snow Leopard can only run J32, not J64. But AFAIK this is to do with the Mac version of J being confined to 32-bit Java for its top-end (Snow Leopard now includes 64-bit Java). The problem may go away (...will go away?) with the new J in beta. Alex's post caught my eye, as a modern variation on multiprocessing a big algorithm as discussed by Eugene McDonnell (1994) in APWJ. Maybe the chapter is still worth reading to cast light on your problem. http://www.jsoftware.com/jwiki/Doc/Articles/Play104 Ian On Tue, Jan 19, 2010 at 5:20 AM, DIETER ENSSLEN <[email protected]> wrote: > thanks > > that would be a shame, that the J program is RAM limited to 2 GB, I assumed > the out of memory problem was hardware and hence pocket book limited. > > So no benefit from 8, 16, 32, 64 etc GB RAM machines, unless running 64 bits > which they would. > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
