time lag when using transactions

Hello,

I notice a time lag of up to 15 seconds when rolling back or commiting a transaction. Is this normal? Does anyone else see this behaviour?

Thanks
Patrick

I tend to have some lag when I rollback but none when I commit.
And somehow it looks like it’s worse when I have Servoy open for a longer period.

To me appears that it takes especially long the FIRST time I cancel a transaction. I do agree, that I also have the impression that a rollback takes longer than a commit.

Yep, committing a transaction is no issue to me but rolling a transaction back can take too much time (at least the user experience is not too good on this part)…

Er, “us too”.

More specifically, a user over a slow line has observed this and today timed a rollback three times: 50sec, 20sec and 20sec. Really quite painful.

This is with Servoy 2.1.2 (server on Linux, java 1.5; client on OSX, java 1.4).

Is there any more useful information we can provide?

Thanks,
Neale.

What database is being used as backend? Does it occurr with small/large/both transactions?

I use the Sybase ASA database and transactions are always small, touching one record only…

The typical transaction I use is single record editing in a formInDialog. So like Marcel’s usage, usually it is a one record transaction.

We’re using mysql 4.0 with Innodb tables, obviously ;-)

JDBC driver is mysql-connector-java-3.0.15-ga-bin.jar

There’s nothing scary about the transactions - typically two to six records (one or two per table) - and the server has a very low load and low concurrency.

Regards,
Neale.

This still is quite an issue for our user experience. My original post was wrong: committing is OK, rollback is the problem. A rollback of a transaction having a single record (foundset size 1) can take up to 30 seconds.

Can this be optimized?

I totally agree… It looks like a rollback takes forever…

Same here with:

Developer
Version R2 2.2rc7-build 325
Java version 1.4.2_04-b05 (Windows XP)
iAnywhere 9.0.1 with default installation

In client or in developer a siingle record rollback now takes 6..8 seconds. . It used not to be so time-expensive.

Same for us, too. Very slow…15 to 30 seconds.

2.2rc7
OS X client
MS SQL Server

Hello Servoy,

is there a comment on this? I am beeing constantly told that this is very annoying…

Thanks
Patrick

Guys,

I don’t use the Mac that often anymore - but it seems to be an OS X issue. When I use Sybase on a PC - the rollback is INSTANT. Same using SQL Server, etc.

Sorry I couldn’t be of more help.

No, sorry. It’s a general issue. I don’t use Macs at all. I have seen this happen on a Windows Server or a Linux Server using MS SQL or ORACLE. Clients are all Windows XP boxes.

OK - interesting. As I’m not part of the engineering team - I don’t have an explanation or solution - sorry.

this is because we have to flush out the caches and read back in.

in the latest build it should be a bit better because not all is queried back in.
Do you guys notice that?

I will look if we can improve even more.

It seems a lot faster now using RC9. If it can be imporved even more - great! Now it is at least 5 times faster.

Thanks!
Patrick

Has this been changed somehow? It seems a lot slower again in the latest builds…

Thanks for looking at this
Patrick