February 2014 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1369) Benchmark performance difference between JacORB and JDK ORB

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1369?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1369: ------------------------------------- Hi Nick, It will be the one from JBTM master: https://github.com/jbosstm/narayana/blob/master/pom.xml#L423 _But_ those numbers are not our final output. We are going to run this in CI regularly alongside some other benchmarking stuff. We are scheduling that work for some time in March - please let me know if you have any input/questions for us. For example, you could raise a PR to upgrade Narayana to JacORB 3 (not necessarily with the intention to merge it) so we can benchmark the numbers for that too. Note that our tests are transaction ones, not EJB ones. Thanks, Tom > Benchmark performance difference between JacORB and JDK ORB > ----------------------------------------------------------- > > Key: JBTM-1369 > URL: https://issues.jboss.org/browse/JBTM-1369 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JTS, Performance Testing > Affects Versions: 4.17.0 > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Fix For: 5.0.2.Final > > > JBTM-934 added support for the JDK orb to JTS. IOR sizes can range in size from 512 bytes to entirely unbounded, with the ORB being able to add arbitrary data within specific portions. Since the IOR is packed into transaction logs and if the IOR sizes are significantly different we may find that transaction throughput has been improved or degraded. We should run some benchmarks to see what the impact is. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1369) Benchmark performance difference between JacORB and JDK ORB

by Nick Cross (JIRA)

[ https://issues.jboss.org/browse/JBTM-1369?page=com.atlassian.jira.plugin.... ] Nick Cross commented on JBTM-1369: ---------------------------------- What version of JacORB was used please? > Benchmark performance difference between JacORB and JDK ORB > ----------------------------------------------------------- > > Key: JBTM-1369 > URL: https://issues.jboss.org/browse/JBTM-1369 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JTS, Performance Testing > Affects Versions: 4.17.0 > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Fix For: 5.0.2.Final > > > JBTM-934 added support for the JDK orb to JTS. IOR sizes can range in size from 512 bytes to entirely unbounded, with the ORB being able to add arbitrary data within specific portions. Since the IOR is packed into transaction logs and if the IOR sizes are significantly different we may find that transaction throughput has been improved or degraded. We should run some benchmarks to see what the impact is. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1369) Benchmark performance difference between JacORB and JDK ORB

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1369?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1369: ------------------------------------- Can you paste in the commands you used to get those numbers, please? > Benchmark performance difference between JacORB and JDK ORB > ----------------------------------------------------------- > > Key: JBTM-1369 > URL: https://issues.jboss.org/browse/JBTM-1369 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JTS, Performance Testing > Affects Versions: 4.17.0 > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Fix For: 5.0.2.Final > > > JBTM-934 added support for the JDK orb to JTS. IOR sizes can range in size from 512 bytes to entirely unbounded, with the ORB being able to add arbitrary data within specific portions. Since the IOR is packed into transaction logs and if the IOR sizes are significantly different we may find that transaction throughput has been improved or degraded. We should run some benchmarks to see what the impact is. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1369) Benchmark performance difference between JacORB and JDK ORB

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1369?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-1369: ---------------------------------------- We have four JTS performance unit tests - they all run 1000 txns, no participants and use different methods to begin a transaction. The results generally show jacorb performance as being significantly better: com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance1 1000 txns (OTSImpleManager.current), no participants (with warm up of 10 txns): idlj Average time for empty transaction = 1.284000039100647 Transactions per second = 778.8161756602676 jacorb Average time for empty transaction = 1.3229999542236328 Transactions per second = 755.8579248680498 com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance2 1000 txns (TSImpleManager.factory().create()), no participants (with warm up of 10 txns): idlj Average time for empty transaction = 3.48799991607666 Transactions per second = 286.6972546045273 jacorb Average time for empty transaction = 2.115999937057495 Transactions per second = 472.5898061181409 com.hp.mwtests.ts.jts.orbspecific.local.performance.Performance3 1000 txns (ArjunaTransactionImple), no participants (with warm up of 10 txns): idlj Average time for empty transaction = 0.05400000140070915 Transactions per second = 18518.5180381656 jacorb Average time for empty transaction = 0.052000001072883606 Transactions per second = 19230.76883399276 com.hp.mwtests.ts.jts.local.synchronizations.Performance 1000 txns (org.omg.CosTransactions.Current) each registering a single synchronization idlj TPS: 191.20458891013382 jacorb TPS: 309.2145949288807 > Benchmark performance difference between JacORB and JDK ORB > ----------------------------------------------------------- > > Key: JBTM-1369 > URL: https://issues.jboss.org/browse/JBTM-1369 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JTS, Performance Testing > Affects Versions: 4.17.0 > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Fix For: 5.0.2.Final > > > JBTM-934 added support for the JDK orb to JTS. IOR sizes can range in size from 512 bytes to entirely unbounded, with the ORB being able to add arbitrary data within specific portions. Since the IOR is packed into transaction logs and if the IOR sizes are significantly different we may find that transaction throughput has been improved or degraded. We should run some benchmarks to see what the impact is. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1369) Benchmark performance difference between JacORB and JDK ORB

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1369?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1369: ------------------------------------- Hi Mike, Lets look at this in the 5.0.2 timeframe. There are a couple of performance test suite issues so we should try to make that the focus of that development cycle. Tom > Benchmark performance difference between JacORB and JDK ORB > ----------------------------------------------------------- > > Key: JBTM-1369 > URL: https://issues.jboss.org/browse/JBTM-1369 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JTS, Performance Testing > Affects Versions: 4.17.0 > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Fix For: 5.0.2.Final > > > JBTM-934 added support for the JDK orb to JTS. IOR sizes can range in size from 512 bytes to entirely unbounded, with the ORB being able to add arbitrary data within specific portions. Since the IOR is packed into transaction logs and if the IOR sizes are significantly different we may find that transaction throughput has been improved or degraded. We should run some benchmarks to see what the impact is. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1453) Reinstate/review the numbers to detect performance regressions

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1453?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1453: -------------------------------- Fix Version/s: 5.0.2.Final (was: 6.0.0.Final) > Reinstate/review the numbers to detect performance regressions > -------------------------------------------------------------- > > Key: JBTM-1453 > URL: https://issues.jboss.org/browse/JBTM-1453 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Performance Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.0.2.Final > > Original Estimate: 3 days > Remaining Estimate: 3 days > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1369) Benchmark performance difference between JacORB and JDK ORB

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1369?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1369: -------------------------------- Fix Version/s: 5.0.2.Final (was: 6.0.0.Final) > Benchmark performance difference between JacORB and JDK ORB > ----------------------------------------------------------- > > Key: JBTM-1369 > URL: https://issues.jboss.org/browse/JBTM-1369 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JTS, Performance Testing > Affects Versions: 4.17.0 > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Fix For: 5.0.2.Final > > > JBTM-934 added support for the JDK orb to JTS. IOR sizes can range in size from 512 bytes to entirely unbounded, with the ORB being able to add arbitrary data within specific portions. Since the IOR is packed into transaction logs and if the IOR sizes are significantly different we may find that transaction throughput has been improved or degraded. We should run some benchmarks to see what the impact is. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2078) BlackTie doesn't build on Fedora 20 64bit

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2078?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2078: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > BlackTie doesn't build on Fedora 20 64bit > ----------------------------------------- > > Key: JBTM-2078 > URL: https://issues.jboss.org/browse/JBTM-2078 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.0.1.Final > > > generate-exe: > libnames not specified or empty. > libnames not specified or empty. > [cc] 1 total files to be compiled. > [cc] /home/tom/projects/jbosstm/narayana/blacktie/btadmin/src/test/cpp/cs.cxx: In function ‘int main(int, char**)’: > [cc] /home/tom/projects/jbosstm/narayana/blacktie/btadmin/src/test/cpp/cs.cxx:31:39: warning: deprecated conversion from string constant to ‘char*’ [-Wwrite-strings] > [cc] putenv("BLACKTIE_CONFIGURATION=linux"); > [cc] ^ > [cc] Starting link > [cc] /lib64/libaprutil-1.so.0: undefined reference to `apr_pool_pre_cleanup_register' > [cc] collect2: error: ld returned 1 exit status -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2050) Add a quickstart showing the JTA 1.2 annotations in use inside WildFly

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2050?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2050: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Add a quickstart showing the JTA 1.2 annotations in use inside WildFly > ---------------------------------------------------------------------- > > Key: JBTM-2050 > URL: https://issues.jboss.org/browse/JBTM-2050 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.0.1.Final > > > For example, it can use @Transactional -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2078) BlackTie doesn't build on Fedora 20 64bit

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2078?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2078: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/599 > BlackTie doesn't build on Fedora 20 64bit > ----------------------------------------- > > Key: JBTM-2078 > URL: https://issues.jboss.org/browse/JBTM-2078 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.0.1.Final > > > generate-exe: > libnames not specified or empty. > libnames not specified or empty. > [cc] 1 total files to be compiled. > [cc] /home/tom/projects/jbosstm/narayana/blacktie/btadmin/src/test/cpp/cs.cxx: In function ‘int main(int, char**)’: > [cc] /home/tom/projects/jbosstm/narayana/blacktie/btadmin/src/test/cpp/cs.cxx:31:39: warning: deprecated conversion from string constant to ‘char*’ [-Wwrite-strings] > [cc] putenv("BLACKTIE_CONFIGURATION=linux"); > [cc] ^ > [cc] Starting link > [cc] /lib64/libaprutil-1.so.0: undefined reference to `apr_pool_pre_cleanup_register' > [cc] collect2: error: ld returned 1 exit status -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues February 2014