[jbossts-announce] Narayana 5.3.3.Final released

[Gytis Trikleris]

I just wanted to update the performance numbers, because the previous email container a week old results. Below are the latest comparison numbers.

Threads           A           B           C           D      Narayana
      1               21          72          34          7           115
     50              31        2349       573      1065        2746

> On 9 Jun 2016, at 12:32, Gytis Trikleris <gytis at redhat.com> wrote:
> 
> Hello,
> 
> The Narayana team are proud to announce the latest release of Narayana!
> 
> The release notes for this version are available from: https://issues.jboss.org/browse/JBTM/fixforversion/12330039 <https://issues.jboss.org/browse/JBTM/fixforversion/12330039>
> 
> Wildfly has had our upgrade merged in so you should see a nightly build of WildFly that includes the upgrade available soon over here:
> https://ci.jboss.org/hudson/job/WildFly-latest-master/ <https://ci.jboss.org/hudson/job/WildFly-latest-master/>
> The commit is: https://github.com/wildfly/wildfly/commit/0314d9bad2a722d9c7e540ed9fb881176aeffb65 <https://github.com/wildfly/wildfly/commit/0314d9bad2a722d9c7e540ed9fb881176aeffb65>
> 
> As is now normal, in this release we compared ourselves against four other leading open source competitor products with a view to checking that the release remains competitive. Results are produced using JMH (a micro benchmark harness created by the OpenJDK project team available from http://openjdk.java.net/projects/code-tools/jmh/ <http://openjdk.java.net/projects/code-tools/jmh/>). We have attempted to configure each product on an equal footing by choosing sensible defaults for each tunable parameter and by ensuring that recovery is enabled, although we do configure narayana with the journal store, which is our best performing transaction log storage mechanism. If you have any recommendations for other transaction managers or how to tune the configuration then please let us know so that we can update our test job. The benchmark runs a transaction containing two dummy resources.
> 
> We will let the figures speak for themselves, suffice to say that when more and more threads are thrown at the workload we scale better showing that we have excellent control over parallelism.
> 
> Threads           A           B           C           D      Narayana
>      1               30          85         29          10          116
>     10              29         615        215       165         595
>     50              28        2082       497       599        2529
> 
> Happy coding,
> The Narayana team

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossts-announce/attachments/20160613/e3435ba7/attachment-0001.html