2:06 p.m.
Hi,
Now that automation of JCR DB compatibility is close to being done, I would like to expand
testing to performance and clustering of JCR outside GateIn similar to how it was done for
identity/picketlink. I had talked to Nicolas during F2F meeting a bit so this is
continuation of that talk as well.
A. Performance Test
- Currently there is standalone perf test suite using japex. Of course, we are going to
first run that in our environment but what kind of confidence this test suite gives you?
- What are the ways to expose JCR service? Nicolas had suggested that webdav would be the
easiest. Given that most of performance test framework we have is towards http end points,
what suggestions you have so that we can reuse the framework we have already?
- What about non web end points?
B. Clustering
-This partly depends on A and having web front end helps over here as well. But I am open
to ideas.
Let's get the ball rolling.
Thanks,
Prabhat
8:08 a.m.
Hi Prabhat,
On Tue, Feb 23, 2010 at 9:06 PM, Prabhat Jha <pjha(a)redhat.com> wrote:
Hi,
Now that automation of JCR DB compatibility is close to being done, I would
like to expand testing to performance and clustering of JCR outside GateIn
similar to how it was done for identity/picketlink. I had talked to Nicolas
during F2F meeting a bit so this is continuation of that talk as well.
A. Performance Test
- Currently there is standalone perf test suite using japex. Of course, we
are going to first run that in our environment but what kind of confidence
this test suite gives you?
The benchmark available http://tests.exoplatform.org/jcr.html are based on
tests on one single node with one and/or several concurrent threads
depending on the test. Compare to the unit tests that we have in JCR, those
tests mainly allow us to quickly identify the performance loss in mono and
multi threads environment and multi-threading errors
- What are the ways to expose JCR service?
Up to now JCR can be exposed through:
- Webdav thanks to our JAX-RS implementation
- FTP
- RMI
Nicolas had suggested that webdav would be the easiest. Given that most of
performance test framework we have is towards http end points, what
suggestions you have so that we can reuse the framework we have already?
We don't know your framework so could you please describe what your
framework need?
- What about non web end points?
We don't know yet, we were wondering if we could test JCR like the JBC Team
tests JBC, i.e. we launch one JVM on each node and in each JVM, we launch a
set of threads. In other words, we could test directly the server side
without any client
B. Clustering
-This partly depends on A and having web front end helps over here as well.
But I am open to ideas.
We have already setup a test with a load-balancer in front and behind a
cluster of JBoss AS, we then test the JCR in cluster through
webdav. Unfortunately, we noticed that 50% of the time was consumed by the
web layers which means that our results are really affected by the web
layers, so we are working on a new way to test it without the web layers to
get pure JCR performances
Let's get the ball rolling.
Thanks,
Prabhat
_______________________________________________
gatein-dev mailing list
gatein-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/gatein-dev
--
Nicolas Filotto
JCR Product Manager
Project Manager
eXo Platform SAS
nicolas.filotto(a)exoplatform.com
+33 (0)6 31 32 92 19
5698
days inactive
5699
days old
1 comments
2 participants
participants (2)
-
Nicolas Filotto -
Prabhat Jha