Not sure. I'm using Processing as my environment, and it's got a preference panel that lets me "Increase maximum available memory." I've bumped that from the default 512MB up to 2048MB. I can go further, I've got 6 GB in the machine, but it can probably address 4 at most. (I'll be installing Snow Leopard on Tuesday, which will probably speed up some of my other QuickTime work, but maybe not Processing. Don't know if it can handle 64 bit natively yet.)
That should be plenty of room. But, IME, Java doesn't work very smoothly on large problems, so it's not terribly surprising.
Can you easily split the arrays? E.g. instead of pixel(x,y,rgb), do rpixel(x,y),gpixel(x,y),bpixel(x,y) sort of thing? Still the same storage space, and not as clean to address, but the individual arrays are smaller.
Comments 3
Reply
Reply
Can you easily split the arrays? E.g. instead of pixel(x,y,rgb), do rpixel(x,y),gpixel(x,y),bpixel(x,y) sort of thing? Still the same storage space, and not as clean to address, but the individual arrays are smaller.
Reply
Leave a comment