Upgrade from 0.21 to 0.23 degraded our app performance significantly

[max-quirk]

Something about our upgrade from 0.21 -> 0.23 caused significant performance degradation in our app:

• DB load increased, particularly non-CPU DB load
• Commit time increased

Has anyone experienced anything similar and how did they deal with it?

We saw that the 0.21->0.22 upgrade migrated fully to SQLAlchemy 2.0 and dropped the databases library. It looks like the default behavior now wraps standalone queries in an implicit BEGIN/COMMIT, and we strongly suspect this is giving us excess commit overhead.

We thought we could set our SQL engine's isolation_level to "AUTOCOMMIT" to put us back to the previous legacy behavior. We're now seeing a bunch of these errors when ormar tries to use savepoints internally:

sqlalchemy.dialects.postgresql.asyncpg.AsyncAdapt_asyncpg_dbapi.Error: <class 'asyncpg.exceptions.NoActiveSQLTransactionError'>: SAVEPOINT can only be used in transaction blocks

Has anyone else successfully patched in AUTOCOMMIT to restore performance, or is the officially recommended path just biting the bullet and wrapping everything in explicit async with database.transaction()? Or how else did people deal with this if encountered? Any advice is appreciated!

[collerek]

Working on it - will publish a newer version soon.

[collerek]

Should be fixed on 0.24.0

[max-quirk]

You da man 👆