> Weblocks computes on each client request the path of the application, > which (if i understand correctly, if not set by the developer > explicitly) is calculated from the path of the ASDF-system to which > the application belongs. For that Weblocks calls asdf:system- > definitions-pathname, which on it's turn traverses all known > directories known to ASDF to search and does a PROBE-FILE for .asd > files with the name of the system searched. And that can take a while. > Not knowing if this is an intendet behavior of Weblocks I implemented > a small function, which memoizes the .asdf locations per system, which > I turn on before loading Weblocks. Then - the demo responds allways in > less than a second.
I'm glad you are addressing this performance issue It is rather expensive computation, considering that it always computes to the same folder once the system is loaded. FYI, dependency also calls it to look up every css/js file. However, I had never notice any slowness. How many registered systems do you have? I'm actually in the middle of implementing a more generic memoization utility so that we can (ideally) pick any function and cache the result. Most of this work has already done by someone else here http://www.tfeb.org/lisp/hax.html#MEMOIZE . At this moment, I'm making it thread safe and adding a few optional caching requirements. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
