There’s some subtlety here about exactly what “zooming” means. In standard implementations, zooming recalculates a small area of the current view, such that the small area has higher precision (“zoomed”), but the rest of the space (“unzoomed”) goes out of frame and the memory gets reused. The end result is the same number of sampled points (“pixels” in the display) each zoom level.
Memory-efficient mandelbrot zooms are an interesting rabbit hole apparently. But I think that with any of them you must store at least one number in full precision. If you zoom 2x/sec then you use minimum 1 bit more ram per second pretty sure. Not certain.
Interesting, I thought that zooming at a constant speed increased RAM usage at a constant rate but I hadn’t checked.
There’s some subtlety here about exactly what “zooming” means. In standard implementations, zooming recalculates a small area of the current view, such that the small area has higher precision (“zoomed”), but the rest of the space (“unzoomed”) goes out of frame and the memory gets reused. The end result is the same number of sampled points (“pixels” in the display) each zoom level.
Memory-efficient mandelbrot zooms are an interesting rabbit hole apparently. But I think that with any of them you must store at least one number in full precision. If you zoom 2x/sec then you use minimum 1 bit more ram per second pretty sure. Not certain.