I recently switched from running weblocks under clbuild to quicklisp. quicklisp tracks dev instead of stable, which is fine since I am just getting started with it. However, page loads which were basically instantaneous, now take 3-4 seconds after clicking _any_ link in the demo app. The traffic is on localhost, and I am running weblocks on a Core2 Duo with Windows 7 32 bit using clozure-cl. The page loads seem cpu bound on the lisp side.
I don't know anything about weblocks' internals, so I'm looking for opinions about what is reasonable to expect. Matt -- You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/weblocks?hl=en.
