[jbossts-issues] [JBoss JIRA] Updated: (JBTM-420) add in-memory (i.e. Volatile) ObjectStore impl.
Jonathan Halliday (JIRA)
jira-events at lists.jboss.org
Wed Dec 17 11:34:54 EST 2008
[ https://jira.jboss.org/jira/browse/JBTM-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Halliday updated JBTM-420:
Fix Version/s: 4.6
Good enough for now, but still room for improvement. As it's only used as an ActionStore not a full ObjectStore, some optimizations can be made e.g. no need to store committed|uncommitted state, it's only ever going to be committed. Also needs better impl of the crash rec methods or crash rec passes will fail noisily rather than silently doing nothing.
> add in-memory (i.e. Volatile) ObjectStore impl.
> Key: JBTM-420
> URL: https://jira.jboss.org/jira/browse/JBTM-420
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Testing, Transaction Core
> Affects Versions: 4.4.0.GA
> Reporter: Jonathan Halliday
> Assignee: Jonathan Halliday
> Fix For: 4.6
> For performance testing purposes it would be nice to have a pure in-memory objectstore implementation. This would store object states in the JVM's RAM and thus facilitate comparisons:
> - comparing driving XAResources directly from the application code vs. via JBossTS would give the overhead of the transaction manager code without any i/o overhead i.e. tell us how performant the transaction manager's 'business logic' is and what the maximum theoretical throughput is if the persistent storage is not a bottleneck. Could also be useful when stress testing or profiling the rest of the transaction manager code.
> - comparing against any other ObjectStore provides figures that show exactly what performance impact that store has i.e. it provides a baseline for evaluating other stores. Previously it's only been possible to compare any given store impl against driving XA resources directly, which does not account for the overhead of the transaction manager code.
> Naturally there's no crash recovery support, so it's totally unsuitable for production usage.
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbossts-issues