28 Jan
2011
28 Jan
'11
4:56 p.m.
On Jan 28, 2011, at 3:44 PM, Sergiu Dumitriu wrote:
On 01/28/2011 12:02 PM, Jerome Velociter wrote:
Nice, probably worth a code snippet on extensions.xwiki.org ;)
When it says "Events" on that page does it include all events (including view
events) or only some events (like only edit events)?
However the issue is that we can't really translate the number of events with the wiki
farm's load, can we?
Thanks
-Vincent
Hi Vincent,
Yes, we can publish some Cacti graphs, for the overall CPU and memory
usage of the machine and HTTP response time.
We don't have tools that detect usages per wiki AFAIK.
We can extract some (edit) statistics from the activity events. Here's a
short summary:
http://www.myxwiki.org/xwiki/bin/Admin/FarmActivityReport Note that we
plan to add a new machine for myxwiki soon, and configure
a load balancer in front of the 2 machines.
Maybe the current machine could be reinstalled from scratch, since the
mysql socket problem isn't solved yet.
Reminder, the problem I'm talking about is that in most myxwiki restart
logs, mysql processlist shows open connection that are in a NULL state
(they're done executing the query and sending the response), while java
lists several threads blocked on reading data from mysql, data that
won't ever come since mysql considers it did all its work.
> Jerome.
>
> On Fri, Jan 28, 2011 at 10:36 AM, Vincent Massol<vincent(a)massol.net> wrote:
>> Hi devs,
>>
>> We're accepting new wikis on myxwiki.org as requests come in but we already
have 110 wikis created on it.
>>
>> When do we know we shouldn't accept new wiki creation on that JVM because
it's degrading performances too much?
>> Do we have tool to monitor wiki activity and publish on a page which wikis are
using the most resources?
>> Do we have tools to display response time stats and see how they evolve over
time?
>>
>> Thanks
>> -Vincent