Yeah, it's fast enough for me too, I was expecting fewer txn/sec.
> But Reaction way is much safer.
> Anyway - if there are good 'algorithm' - this is the solution. And
> perfect algorithm may be improved with "C implementation".
> But nobody can reduce O(n*2) to O(log(n)),
I definitely agree that correct behavior is more important than speed.
> Trivial case for atomic/modifier is not interesting for me because
> this one really don't touch 'nested transaction operations'.
> I believe - after Reaction learn how to process "partial rollbacks/
> retries" total benchmark will show: Reaction wins.
Well, most txns do not need retries at all -- it could make startup of
some particularly large app faster, but during normal operation rules
should generally run without retries.
Also, I'm not sure Reaction will get faster than Trellis w/o resorting
to compiled extensions (well, maybe, but I don't care about it too
much). Anyway I'd expect the speed difference to be much smaller for
regular "meaty" txns.
--
Best Regards,
Sergey Schetinin
http://s3bk.com/ -- S3 Backup
http://word-to-html.com/ -- Word to HTML Converter