An interesting example of performance using SQL workers and different tricks...

Sten-Erik Björling s-e.bjorling at
Mon Nov 28 15:39:43 UTC 2022

Hi all,

BTW - the search performed involved a seven table join...

Done some testing after some optimisation using the DVD Rental example database running on PostgreSQL 15 on a MacBook Pro Max with a 5-client web server….

Calls per second: 350
Processing load on one processor: 46%
The number of active connections to PostgreSQL: 5 (equal load distribution).

Of course, there will be latencies etc. involved in a real implementation but this performance is impressive. A 10-user license might achieve close to 650 calls per second with a full load on one processor core.

Good to know - especially since an optimal server structure for a small implementation is an Apple Studio Max - drawing around 30 Wats for all CPU cores. For one core maybe a total of 15 watts…

Take care, all the best…



Sten-Erik Björling
Enviro Data
Kyrkogatan 5A 2 tr
SE-972 32  Luleå

E-Mail: s-e.bjorling at
Mobile: +46-70-655 11 72
Wire: @stenerikbjorling
Skype: stenerikbjorling
iChat: stene at
Signal: +46 70 655 11 72
FaceTime: stene at
Telegram: @stenerikbjorling
Hotmail / Messenger: stenerikbjorling at
GMail: stenerikbjorling at

This email and any files transmitted with it are confidential, may be legally privileged and are intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient, please note that any use, distribution, or reproduction of the contents of this email is strictly prohibited and may be unlawful. If you are not the intended recipient, please notify the sender by return email and destroy all copies of the original message including any attachments thereto. Thank you.

Please note that we take reasonable precautions to prevent the transmission of viruses; however, we cannot guarantee that this email or its attachments are free from viruses. We only send and receive emails on the basis that we are not be liable for any loss or damage resulting from the opening of this message and/or attachments.

More information about the omnisdev-en mailing list