August 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-723) Proper collection rollback

by Ben Wang (JIRA)

Proper collection rollback -------------------------- Key: JBCACHE-723 URL: http://jira.jboss.com/jira/browse/JBCACHE-723 Project: JBoss Cache Issue Type: Sub-task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Fix For: 2.0.0 It is not properly yet via the undointerceptor -- 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, 11 months

2
3
0 / 0

[JBoss JIRA] Closed: (JBCACHE-562) Disable cache loader when no cacheloader class is specified

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-562?page=all ] Manik Surtani closed JBCACHE-562. --------------------------------- Fix Version/s: (was: 2.0.0.GA) Resolution: Rejected > Disable cache loader when no cacheloader class is specified > ----------------------------------------------------------- > > Key: JBCACHE-562 > URL: http://jira.jboss.com/jira/browse/JBCACHE-562 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Priority: Minor > > In 1.3, we support a new form of cacheloader config. However, it is incovenient to disable the cache loader (previously all we need is to specify cacheloaderclass to empty). We should also support this kind of semantics so we can disable it easily. I propose when do createcacheloader, we also check whether the class name is there or not to decide whether to go ahead. If not, we simply log an info message. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBCACHE-432) PropertyConfigurator: investigate how to implement parsing functionality without use of PropertyEditor

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-432?page=all ] Manik Surtani closed JBCACHE-432. --------------------------------- Fix Version/s: (was: 2.0.0.GA) Resolution: Rejected > PropertyConfigurator: investigate how to implement parsing functionality without use of PropertyEditor > ------------------------------------------------------------------------------------------------------ > > Key: JBCACHE-432 > URL: http://jira.jboss.com/jira/browse/JBCACHE-432 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 1.2.3, 1.2.4beta, 1.2.4, 1.2.4SP1 > Reporter: Bela Ban > > Can you look into whether this is feasible ? If not, can you move this issue to 1.4 ? > If we could get rid of that class, we could remove jboss-common.jar -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (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 closed JBCACHE-469. --------------------------------- Fix Version/s: (was: 2.0.0.GA) Resolution: Rejected > 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 > > 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, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (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 closed JBCACHE-519. --------------------------------- Fix Version/s: (was: 2.0.0.GA) Resolution: Rejected > 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 > > 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, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBCACHE-508) JBossCache bechmark and performance tuning

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-508?page=all ] Manik Surtani closed JBCACHE-508. --------------------------------- Fix Version/s: (was: 2.0.0.GA) Resolution: Rejected > JBossCache bechmark and performance tuning > ------------------------------------------ > > Key: JBCACHE-508 > URL: http://jira.jboss.com/jira/browse/JBCACHE-508 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Ben Wang > > I have created this task specifically to document our effort in the bechmark and performance tuning process. I am using this tool that I developed to do perf test:http://jira.jboss.com/jira/browse/JBCACHE-503 > Note this load test only emulates the http session pattern now. > I will document the numbers here that I have found and discussed with Bela. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBCACHE-478) Translate docs into Italian

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-478?page=all ] Manik Surtani closed JBCACHE-478. --------------------------------- Fix Version/s: (was: 2.0.0.GA) Resolution: Rejected > Translate docs into Italian > --------------------------- > > Key: JBCACHE-478 > URL: http://jira.jboss.com/jira/browse/JBCACHE-478 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 1.2.4SP1 > Reporter: Manik Surtani > Priority: Minor > > Translating JBoss Cache documentation to Italian. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBCACHE-544) Remove AbstractNode superclass

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-544?page=all ] Manik Surtani closed JBCACHE-544. --------------------------------- Fix Version/s: (was: 2.0.0.GA) Resolution: Rejected > Remove AbstractNode superclass > ------------------------------ > > Key: JBCACHE-544 > URL: http://jira.jboss.com/jira/browse/JBCACHE-544 > Project: JBoss Cache > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Affects Versions: 1.3.0.GA > Reporter: Elias Ross > > If AbstractNode is not used anywhere, it's basically more code to maintain. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBCACHE-553) JBossCache throughput II

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-553?page=all ] Manik Surtani closed JBCACHE-553. --------------------------------- Fix Version/s: (was: 2.0.0.GA) Resolution: Rejected > JBossCache throughput II > ------------------------ > > Key: JBCACHE-553 > URL: http://jira.jboss.com/jira/browse/JBCACHE-553 > Project: JBoss Cache > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Here are the results using the perf test to run our Atl clustering lab. The machines are: 2X 3.0GHZ Xeon, 4GB Ram, GBSwtich, dedicated, 140GB drive. > The load condition are: > 400 clients (total), no sleep, 7kbyte payload > async: > Cluster size, throughtput (req/sec) > 8, 1270 (8.9MB/sec) > 4, 1270 > 2, 1400 > sync: > Cluster size, throughtput (req/sec) > 8, 432 (3.0MB/sec) > 4, 480 > 2, 700 -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (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 closed JBCACHE-328. --------------------------------- Fix Version/s: (was: 2.0.0.GA) Resolution: Rejected > 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 > > 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, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2007