What could be the best method for storing Mandelbrot values ​​in a database?

I'm currently experimenting with rendering the Mandelbrot set, and I quickly realized that it would be useful not to recount the maximum number of iterations for each rendering ... on the other hand, this is a lot of data to keep track of. It seems to me (based on my limited experience with RDMS) that a relational database is probably not suitable, because I do not want performance to affect the increase in the data set. It almost seems like an ideal situation for a hash table, but I have never used it before and cannot figure out how to use it or manage it in one of the existing web server languages ​​(Python / PHP / whatever).

To be a little more explicit: the important values ​​to keep are:

  • the original real part of the number on the complex plane
  • the original imaginary part of the number on the complex plane
  • The number of maximum iterations
  • The number of completed iterations n until the maximum iterations are reached or until the point disappears ad infinitum
  • the final real part of the number on the complex plane after n iterations
  • final imaginary part of the number on the complex plane after n iterations

, , , .

? - ? ?

. !

Edit

julienaubert.

, ( ). , x y, . , ( max_iter, real_final imag_final), , , , , .

:

http://jsfiddle.net/xfF3f/

drawMandelbrot(), , , . drawMandelbrotFromData(), , .

"cleardabrot", . "refilldabrot", drawMandelbrotFromData()... , , , .

, , , , (, , ... , , - ), . ...

  • 300x300.
  • , x = .000001 y = .0000231.
  • w = .00045 h = .00045

, , 300 * 300 ( ), , . ... , x, y, w h .

+5
1

, , , .

, ? ?

, max_iterations, , , /. .

, , ( ), , , .

, , . , , .

  • ( origo_real, origo_imag, max_iter)
  • (final_real, final_imag, actual_iter)

, / , , , L1 L2.

... , .

, , , ... , :)

(/, ), .

, , , , . , , , ( ).

. , , . , , . .

, , ( ). , , , , Google Maps/GIS . , , , - (, , )

, , / -, , .

+2

All Articles