On Donnerstag, 27. Dezember 2007, cnit wrote:
(2) Query answering is done without any caching, and this is clearly a
problem. While inline queries are computed only once and stored in the
parser cache afterwards, Special:Ask has no caching facility at all. This
needs to change in the
Forget my previous post. The problem goesaway when I removed one
template. It seems the performance issue is related tothe
application instead of the database.
Try setting up eAccelerator for PHP, maybe it would help a bit. Also,
I believe that MW/SMW requires dedicated server (co-location).
Well, that is not the case for the current parser cache, neither in MW nor in
SMW. But if course it could be achieved with some server-side cronjobs.
Ah, I didn't knew about MW cronjobs. That sounds nice. Will try to
find out some examples. Maybe you're right that such functionality
shouldn't
On Freitag, 28. Dezember 2007, cnit wrote:
Well, that is not the case for the current parser cache, neither in MW
nor in SMW. But if course it could be achieved with some server-side
cronjobs.
Ah, I didn't knew about MW cronjobs. That sounds nice. Will try to
find out some examples. Maybe
On Freitag, 28. Dezember 2007, Yaron Koren wrote:
How about ~%substring% instead? The ~ is the symbol for pattern matching
in Perl and some UNIX languages, and it might be a clearer indicator of
function than %.
I would immediately use that, but IFRC the Halo extension has a similar syntax
A lot of people are accustomed to the ? (single-character match) and *
(multi-character match) format. It would be easy to escape the '_'s and
'%'s in a match and then do a replace of ? to _ and * to %. (A little
preg and \ could still easily escape those.)
I don't know about ~ though, in the
