Hi all,
during the 5.2 cycle I added some parsers which enabled reading in the
infinispan subsystem configuration from AS7/JDG/EAP. While the parsers
are actually fine, we are still not able to parse the jgroups and
threads subsystem configuration which are essential elements of a full
Now the suite is forks a new process for each module. I've complete the run
with 128m MaxPerm.
On 20 Mar 2013, at 23:55, Sanne Grinovero wrote:
Thanks Dan,
with the following options it completed the build:
MAVEN_OPTS=-server -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode
-XX:+UseParNewGC
On Wed, Apr 17, 2013 at 5:53 PM, Manik Surtani msurt...@redhat.com wrote:
On 17 Apr 2013, at 08:23, Dan Berindei dan.berin...@gmail.com wrote:
I like the idea of always clearing the state in members of the minority
partition(s), but one problem with that is that there may be some keys that
On 18 Apr 2013, at 06:44, Dan Berindei dan.berin...@gmail.com wrote:
On Wed, Apr 17, 2013 at 5:53 PM, Manik Surtani msurt...@redhat.com wrote:
On 17 Apr 2013, at 08:23, Dan Berindei dan.berin...@gmail.com wrote:
I like the idea of always clearing the state in members of the minority
via XSLT? +1.
On 18 Apr 2013, at 04:57, Tristan Tarrant ttarr...@redhat.com wrote:
Hi all,
during the 5.2 cycle I added some parsers which enabled reading in the
infinispan subsystem configuration from AS7/JDG/EAP. While the parsers
are actually fine, we are still not able to parse the
On 04/18/2013 03:28 PM, Manik Surtani wrote:
via XSLT? +1.
Yep.
Tristan
___
infinispan-dev mailing list
infinispan-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
From a support standpoint, I'd prefer the converters.
It should be easier to debug any issues specific to one configuration
parser.
(It would have been MUCH better to only have one configuration format
for everything, but it's too late for that now...)
-Dennis
On 04/18/2013 02:57 AM, Tristan
Can't we converge on one format in the future?
As any converted or dual parser will have it's own set of bugs.
What we could do in the short time is a function which dumps the full
configuration; I'm quite fond of this capability in JGroups to dump
all its stack configuration as an XML, so I
On 18 Apr 2013, at 14:33, Sanne Grinovero sa...@infinispan.org wrote:
Can't we converge on one format in the future?
As any converted or dual parser will have it's own set of bugs.
What we could do in the short time is a function which dumps the full
configuration; I'm quite fond of this
Guys,
Based on some recent micro benchmarks I've been doing, I've seen:
MapStressTest configuration: capacity 10, test running time 60 seconds
Testing mixed read/write performance with capacity 100,000, keys 300,000,
concurrency level 32, threads 12, read:write ratio 0:1
Container CHM
On 04/18/2013 09:35 PM, Manik Surtani wrote:
Guys,
Based on some recent micro benchmarks I've been doing, I've seen:
MapStressTest configuration: capacity 10, test running time 60 seconds
Testing mixed read/write performance with capacity 100,000, keys 300,000,
concurrency level 32,
11 matches
Mail list logo
