Good news! With the add-line change that freeze operation on that huge fractal
finished!
time(img-expr): cpu time: 1552529 real time: 1567217 gc time: 576576
time(freeze(img)) : cpu time: 26904587 real time: 79234417 gc time: 20568080
What is that, about 7 and a half hours of cpu time, about
One of the issues is that the racket/draw version is not doing the
cropping that the 2htdp/image version is doing. Changing the
scene+line call in utils.rkt to add-line cuts the freeze time in
half for me (using size 242 instead of 728 in the time.rkt file). I
didn't check to see if lines go
On May 5, 2015, at 10:06 AM, Robby Findler ro...@eecs.northwestern.edu wrote:
One of the issues is that the racket/draw version is not doing the
cropping that the 2htdp/image version is doing. Changing the
scene+line call in utils.rkt to add-line cuts the freeze time in
half for me (using
On May 4, 2015, at 6:02 PM, Robby Findler ro...@eecs.northwestern.edu wrote:
Another approach here would be to help me do performance debugging of
2htdp/image :). You could write the code directly as imperative calls
to the dc% interface and see how that compares. If there's a
significant
I’m trying to use 2htdp/image to generate images of fractals.
But while generating the images is “relatively” quick, it is freezing the
images that’s taking a long time.
For the most complicated one, I started it running two nights ago, and the
freeze operation on it still hasn’t finished.
5 matches
Mail list logo
