Resources are cheap only when projects are not popular - when they get
popular, resources become very expensive.
Yeh, Video editing spoils people ;)
Sergey
On Dec 30, 2007 4:58 AM, cnit <[EMAIL PROTECTED]> wrote:
> > Yes, but just throwing resources at something doesn't make it efficien
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 r
> Yes, but just throwing resources at something doesn't make it efficient.
Resources are cheap. Even major server brands such as HP have moved their
production to China.
OK, I am doing videoediting among other things, that's why I am for hardware
resources.
> As for code cache/accelerator, I ag
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
securi
Yes, but just throwing resources at something doesn't make it efficient.
As for code cache/accelerator, I agree - improvement is quite big because MW
is doing lots of includes plus MW can use it for cache as well - I use APC
and it works pretty good.
Sergey
On Dec 28, 2007 6:36 AM, cni
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 t
> We have a set of semantic queries in a template. Thattemplate is
> used in some pages. However, by looking at the database processlist,
> it seems that those set of queries are processed whenever a page
> isrequested, even when the template is not used by the requested
> page (e.g.special pages).
> 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).
Forget my previous post. The problem goes away when I removed one
template. It seems the performance issue is related to the application
instead of the database.
From: Wang, Alex (NIH/CIT) [E]
Sent: Thursday, December 27, 2007 4:46 PM
To: semediawiki-devel@lis
