On Fri, Mar 20, 2009 at 12:00 PM, Plamen Stamov <[email protected]> wrote: > I'm really new to weblocks, so my question: is this cpu/time-burning > something inherent to the current architecture of weblocks, if yes - > is there a hope to have it better? Something's wrong. All the actions you mentioned should take no more than a split second. I've never encountered this before, and I did some testing on Lispworks.
Do you have access to a profiler that you could run to narrow down the problem? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
