On Sonntag, 30. Dezember 2007, Sergey Chernyshev wrote:
Hmm. I didn't realize there is a way to remove $smwgQDefaultNamespaces
restriction and this will enable all namespaces instead of disabling them.
Why is it that this setting not set to NULL by default then? I don't see
any point in
On Freitag, 28. Dezember 2007, Lau, William (NIH/CIT) [E] wrote:
We have a set of semantic queries in a template. That template is used
in some pages. However, by looking at the database process list, it
seems that those set of queries are processed whenever a page is
requested, even when the
Hmm. I didn't realize there is a way to remove $smwgQDefaultNamespaces
restriction and this will enable all namespaces instead of disabling them.
Why is it that this setting not set to NULL by default then? I don't see any
point in restricting namespaces unless it's absolutely necessary for
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).
@lists.sourceforge.net
Subject: [SMW-devel] SMW performance
It is very slow (30 seconds) to open any pages including Main Page.
Checking the processes in mysqld found the following sql statements for
each page respectively. I guess `prop11`, `prop8`, `cats6` are temporary
tables, which make it hard
