Just to narrow down the issue: when you disable the S3 cache store, I
assume the performance problem goes away, correct ?
Just trying to pin the blame on the S3 cache loader, then I don't even
need to see whether it is a JGroups problem... :-)
philippe van dyck wrote:
Hi Infinispan mailing list,
a couple of days ago, I succeeded in writing an entity store for qi4j
(
http://www.qi4j.org/) using Infinispan, the S3 store and the S3_PING JGroups clustering
configuration.
It works like a charm, discovers new EC2 instances, synchronizes and process transactions
perfectly... you did an amazing job.
But I have a serious performance problems.
When I write an update (<1k) to the cache, it takes around 500 ms to be stored on S3.
The best result I achieved was around 10 cache writes per second... it is abysmal (when
using httpclient directly I had a min of 100/sec using 20 connections).
When I commit a JTA transaction made of 100 cache writes, it takes around 30 seconds
(cpu<5%) and the first write ends on S3 after at least 5 seconds of 'idle' time
(SSL negotiation??).
I disabled the store asynchronism and work without JTA transactions, no effect on
performance.
I also modified the jClouds configuration, multiplying by 10 all worker threads,
connections and the rest... no improvement!
When I (load) test my web app (wicket based+qi4j+...infinispan) the cpu stays idle
(<5%) and ... JTA transactions fails (timeouts) and I cannot acquire locks before the
10 seconds timeout.
Is there something fishy in the jclouds configuration ? in the httpnio use of jclouds ?
in the version of jclouds (the trunk one with the blob store seems to be so different) ?
Am I missing something ?
Any pointer to any doc/help/experience is welcome ;-)
Philippe
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Bela Ban
Lead JGroups / Clustering Team
JBoss