Uploaded image for project: 'JBoss Transaction Manager'
  1. JBoss Transaction Manager
  2. JBTM-420

add in-memory (i.e. Volatile) ObjectStore impl.

    XMLWordPrintable

    Details

      Description

      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.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                jhalliday Jonathan Halliday
                Reporter:
                jhalliday Jonathan Halliday
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: