> On Dec 12, 9:08 am, "Leslie P. Polzer" <[email protected]>
> wrote:
>
> > > It's a shame rendering 1,400 links takes 7 seconds, but I think that's
> > > the cost of closures unless i'm mistaken
>
> > I'm not entirely convinced of that and will check this out.
>
> Revision caf62ebf2d1b fixes RENDER-LINK speed.
>
>   Leslie
Changes certainly fix render-link.  Thank you!  What's odd (as I have
no clue how this could be happening given that the memoization appears
to be working) cached-sysdef-central-registry-search is still taking a
boatload of time:

CL-USER> (weblocks:reset-sessions)
  seconds  |    consed   |  calls |  sec/call  |  name
----------------------------------------------------------
     4.431 | 306,962,624 |    612 |   0.007240 | AW::CACHED-SYSDEF-
CENTRAL-REGISTRY-SEARCH
     0.093 |   1,398,512 |     97 |   0.000959 | WEBLOCKS:RENDER-LINK
     0.065 |   4,750,048 |    306 |   0.000212 | WEBLOCKS:MAKE-LOCAL-
DEPENDENCY
     0.064 |   5,164,592 |      2 |   0.031995 | WEBLOCKS:REDIRECT
     0.058 |   4,623,040 |      7 |   0.008345 | AW::MAKE-CHILDREN
     0.041 |     586,048 |    307 |   0.000134 | WEBLOCKS:COMPUTE-
PUBLIC-FILES-PATH
     0.028 |   1,170,816 |    111 |   0.000249 | AW::AWLOG

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?

--

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