[JBoss JIRA] Reopened: (JBCACHE-469) JGroups Channel reference to be obtained from a factory
by Manik Surtani (JIRA)
[ http://jira.jboss.com/jira/browse/JBCACHE-469?page=all ]
Manik Surtani reopened JBCACHE-469:
-----------------------------------
Assignee: (was: Manik Surtani)
> JGroups Channel reference to be obtained from a factory
> -------------------------------------------------------
>
> Key: JBCACHE-469
> URL: http://jira.jboss.com/jira/browse/JBCACHE-469
> Project: JBoss Cache
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Affects Versions: 1.2.4
> Reporter: Manik Surtani
> Fix For: 2.0.0.GA
>
>
> The JChannelFactory (will be available in JGroups 2.3 - see JGRP-112) should be used to get a channel instance.
> The JChannelFactory could be obtained by:
> 1) MBeanServer lookup (look up a JChannelFactoryMBean instance)
> JBossCache config will need:
> + JChannelFactoryMBean name
> + JGroups configured stack name
> JBossCache config will not need:
> - Cluster name
> - JGroups settings
> 2) JChannelFactory instantiation
> JBossCache config will need:
> + Cluster name
> + JGroups settings
> JBossCache config will not need:
> - JChannelFactoryMBean name
> - JGroups configured stack name
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 4 months
[JBoss JIRA] Reopened: (JBCACHE-519) Investigate why tx has a higher thruput than non-tx under perf test
by Manik Surtani (JIRA)
[ http://jira.jboss.com/jira/browse/JBCACHE-519?page=all ]
Manik Surtani reopened JBCACHE-519:
-----------------------------------
Assignee: (was: Manik Surtani)
> Investigate why tx has a higher thruput than non-tx under perf test
> --------------------------------------------------------------------
>
> Key: JBCACHE-519
> URL: http://jira.jboss.com/jira/browse/JBCACHE-519
> Project: JBoss Cache
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Reporter: Ben Wang
> Fix For: 2.0.0.GA
>
>
> During the perf test, I have discovered that the throughput with tx is higher than the non-tx one. This is very puzzling. I have asked Scot Marlow to double check it for me. The same.
> Machines are: dev09 and dev17.
> Here are some breakdown numbers:
> 1. Single thread, 3000 loops, 10 ms sleep interval.
> (a) no tx
> -----
> Total time spent (ms) per thread: 202921 for 3000 loops
> Throughtput for this node with:
> threads = 1
> loops = 3000
> sleep interval = 10
> object list size = 100
> tranasaction? false
> is: 14 requests/sec
> (b) tx
> ----
> Total time spent (ms) per thread: 200718 for 3000 loops
> Throughtput for this node with:
> threads = 1
> loops = 3000
> sleep interval = 10
> object list size = 100
> tranasaction? true
> is: 14 requests/sec
> 2. 100 threads, 0ms sleep interval
> (a) no tx
> -----
> Total time spent (ms) per thread: 49352 for 400 loops
> Throughtput for this node with:
> threads = 50
> loops = 400
> sleep interval = 0
> object list size = 100
> tranasaction? false
> is: 404 requests/sec
> -----
> Total time spent (ms) per thread: 61240 for 400 loops
> Throughtput for this node with:
> threads = 50
> loops = 400
> sleep interval = 20
> object list size = 100
> tranasaction? false
> is: 325 requests/sec
> -------- dev04
> Total time spent (ms) per thread: 78871 for 400 loops
> Throughtput for this node with:
> threads = 50
> loops = 400
> sleep interval = 20
> object list size = 100
> tranasaction? false
> is: 250 requests/sec
> (b) tx
> -----
> Total time spent (ms) per thread: 68770 for 400 loops
> Throughtput for this node with:
> threads = 50
> loops = 400
> sleep interval = 0
> object list size = 100
> tranasaction? true
> is: 288 requests/sec
> ----
> Total time spent (ms) per thread: 74575 for 400 loops
> Throughtput for this node with:
> threads = 50
> loops = 400
> sleep interval = 20
> object list size = 100
> tranasaction? true
> is: 263 requests/sec
> --- dev04
> Total time spent (ms) per thread: 80648 for 400 loops
> Throughtput for this node with:
> threads = 50
> loops = 400
> sleep interval = 20
> object list size = 100
> tranasaction? true
> is: 242 requests/sec
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 4 months
[JBoss JIRA] Reopened: (JBCACHE-328) Move attributes and getters/setters to interceptors
by Manik Surtani (JIRA)
[ http://jira.jboss.com/jira/browse/JBCACHE-328?page=all ]
Manik Surtani reopened JBCACHE-328:
-----------------------------------
Assignee: (was: Manik Surtani)
> Move attributes and getters/setters to interceptors
> ---------------------------------------------------
>
> Key: JBCACHE-328
> URL: http://jira.jboss.com/jira/browse/JBCACHE-328
> Project: JBoss Cache
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Bela Ban
> Fix For: 2.0.0.GA
>
>
> Example: currently IsolationLevel is an attribute of TreeCache. Goal is to make it an attribute of PessimisticLockingInterceptor.
> Advantage:no unneeded methods in TreeCache, cluttering up the TreeCache class
> #1 Implicit Configuration (conceptual)
> --------------------
> <TreeCache>
> <Replication>
> <config> ... </config>
> <mode>ASYNC</mode>
> </Replication>
> <IsolationLevel>
> REPEATABLE-READ
> </IsolationLevel>
> </TreeCache>
> This configures the interceptor chain
> #2 Explicit configuration
> ------------------------------------
> <TreeCache>
> <Interceptor name="PessimisticLockingInterceptor"
> class="xxxx"
> level="REPEATABLE-READ" />
> <Interceptor>...</Interceptor>
> </TreeCache>
> The chain is defined explicitly, attributes are defines per interceptor
> #3 JMX
> If JMx is used, JBossCache is registered with the MBeanServer, and all interceptors are registered under JBossCache, e.g.
> type=cache;name=JBossCache1
> type=cache;name=JBossCache1;interceptor_name=PessimisticLockingInterceptor
> type=cache;name=JBossCache1;interceptor_name=CacheLoaderInterceptor
> type=cache;name=JBossCache1;interceptor_name=ReplicationInterceptor
> #4 Programmatic access
> Can be done through JMX, but is not nice
> cache.getIsolationLevel() --> ((PessimisticLockingInterceptor)cache.getInterceptor("PessimisticLockingInterceptor")).getIsolationLevel()
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 4 months