> AW> (hash-keys *asdf-cache*)
> ("weblocks-prevalence" "bordeaux-threads" "cl-prevalence" "s-sysdeps"
> "s-xml"
>  "cl-ppcre" "metatilities" "asdf-system-connections" "metabang-bind"
>  "cl-containers" "metatilities-base" "moptilities" "closer-mop"
> "weblocks"
>  "weblocks-memory" "trivial-timeout" "salza2" "f-underscore"
> "anaphora" "md5"
>  "cl-cont" "fare-matcher" "fare-utils" "cl-fad" "sb-posix" "sb-grovel"
>  "parenscript" "cl-who" "cl-json" "puri" "hunchentoot" "usocket"
>  "sb-bsd-sockets" "split-sequence" "rfc2388" "cl+ssl" "flexi-streams"
>  "trivial-gray-streams" "cffi" "babel" "alexandria" "trivial-features"
>  "cl-base64" "chunga")
>
> Any ideas?

I'm an idiot.  It wasn't caching the very system I was looking for (aw
is the name of the webapp).  So I added a symbolic link in the /usr/
local/lib/sbcl/site-systems folder to the webapp's .asd file.  That
did the trick.  I suppose the other option is to add the director to
the asdf:*central-registry*.

I was under the false impression that simply loading the .asd and
relevant package files (along with the entire webapp eventually) into
the lisp interpreter would update asdf such that it'd return the
correct path when querying for a system.

The times now are:
  seconds  |   consed   |  calls |  sec/call  |  name
---------------------------------------------------------
     0.471 |  4,794,432 |    310 |   0.001518 | WEBLOCKS:RENDER-LINK
     0.419 | 22,274,896 |  2,316 |   0.000181 | AW::AWLOG
     0.145 | 13,334,848 |    982 |   0.000148 | WEBLOCKS:MAKE-LOCAL-
DEPENDENCY
     0.059 |  4,379,008 |    996 |   0.000059 | WEBLOCKS:COMPUTE-
WEBAPP-PUBLIC-FILES-PATH
     0.051 |  5,967,056 |    310 |   0.000166 | WEBLOCKS::GENERATE-
ACTION-CODE
     0.046 |  4,647,600 |      7 |   0.006630 | AW::MAKE-CHILDREN
     0.044 |     37,536 |  3,259 |   0.000014 | WEBLOCKS:ATTRIBUTIZE-
NAME
     0.036 |  1,750,384 |    320 |   0.000112 | WEBLOCKS:DOM-CLASSES
     0.035 |  1,445,936 |    997 |   0.000035 | WEBLOCKS:COMPUTE-
PUBLIC-FILES-PATH

Thanks to everyone for all the help!

--

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.


Reply via email to