--- Comment #4 from John Cardinal <> 2010-03-03 22:26:33 
EST ---
I did not know about the performance impact of being logged in. I logged out
and visited a couple pages with lots of citations and saw the effect you

I also looked at the citation templates again and I'd like to try and convince
you (and others) that #wrap is worth it. I certainly understand that an
algorithmic improvement (such as the caching mechanism you described) will
yield a much bigger improvement than fine-tuning template code, but algorithmic
improvements tend to be a lot more work, and they are more risky. On the other
hand, #wrap should be easy to implement and easy to test. It has to yield some
improvement, so worst-case, it's provides a small performance improvement and a
nice-to-have feature in terms of code clarity, and any time saved at all is

I'd love to see a redesign of the template facility, perhaps implemented as a
separate facility. (Leave templates in place, but add a new facility with
syntax that isn't "totally insane" <g>.) I presume one hard part is designing a
powerful facility that integrates with a caching system. I am not sure if there
are any content management systems with a similar facility, but I recall that
XSLT was designed as a declarative language in part to enable progressive
rendering and specifically, to allow transforming part of a document without
transforming the rest. I can't say that it succeeded; I used XSLT a lot but I
am not familiar with the innards of any XSLT processors.

Thanks again for engaging this issue. If there is a place where WP
technologists are discussing these sorts of issues, I'd love to know about it
and participate.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.
You are on the CC list for the bug.

Wikibugs-l mailing list

Reply via email to