[gatein-dev] Fix in portal list

[Prabhat Jha]

Are these stats on by default? What is the overhead of getting these metrics? BTW: It's awesome data to have. 

----- Original Message -----
From: "Julien Viet" <julien at julienviet.com>
To: gatein-dev at lists.jboss.org
Cc: "Wesley Hales" <whales at redhat.com>, "Marek Posolda" <mposolda at redhat.com>
Sent: Monday, November 16, 2009 4:28:20 AM GMT -06:00 US/Canada Central
Subject: [gatein-dev] Fix in portal list

I want to bring to you that useful following statistic available via  
JMX, specially in JBoss where you can use the JMX console.

Wesley has been using it for his bridge demo (and I fixed the bug that  
was present Wes :-) ).

I believe also that Marek could collect information during load  
testing and create graphs that would be correlated with the  
performances graphs. (for instance , showing the portal throughput and  
the average response time on the same graph, or showing the usage of  
the various caches correlated with the througput, I guess you get the  
idea).

With the JMX console, the statistics are interesting but it remains  
limited, it becomes very useful only if we can exploit the data via a  
more powerful tool with charting and gauges.

1/ service=statistic,type=portal,view=portal

- gives you the list of portal ids
- for a given portal id you can get info like:
1/ average execution time
2/ minimum execution time
3/ maximum execution time
4/ execution count (can be graphed)
5/ throughput, i.e number of request per second (can be graphed)

2/ service=statistic,type=template,view=portal

- list of the 10 slowest templates
- list of the 10 fastest templates
- list of the 10 most used templates
- list of all template ids
- for each template it is possible to have info about:
1/ average time
2/ min time
3/ max time
4/ execution count

3/ service=SessionRegistry

it gives the list of the number of active JCR session in the portal  
which can be graphed as it gives a good indicator of the load on the  
server

4/ each cache is registered under the key  
name="$CACHE_ID",service=cache which gives the usual information

there are other few mbeans available but they are less interesting, so  
I won't talk much about it.

cheers

Julien
_______________________________________________
gatein-dev mailing list
gatein-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/gatein-dev