Brad Beveridge writes: > All functions that should really be non-consing & very quick, and > probably inline too. I think that R, G, B, A functions are slow due > to the way that Lispbuilder stores color as a vector, rather than a > (simple-array (unsigned-byte 8)), though it maybe should even be an > (unsigned-byte 32). > I couldn't work out why FP was consing/slow, I assume that is an SBCL > problem with auto generated CLOS reader functions. > > Anyhow, I don't know if anybody cares :)
I care. I started looking into this a couple of weeks ago, after I profiled one of the random rectangle examples over a 90 minute period and found that it CONS'ed several hundred gigabytes of RAM. What makes things worse is that a function can be called ~60 times a second, so any small amount CONSing really starts to add up after a few seconds. Does anyone have any experience in CL optimization? - Luke _______________________________________________ application-builder mailing list [email protected] http://www.lispniks.com/mailman/listinfo/application-builder
