Currently identified situation.
When there was an attempt to create the “internal correspondence” process at the same time, the Bitronics logs prescribed a timeout, but in fact Postgres worked, and the monitoring increased the length of the disk queue (the delay was up to 10 ms).
After 1-2 minutes, the process worked as usual and I managed to create 10 processes.
During the timeout, other processes, including service.
I ask you to correct this error.
Bonita 7.8.4(RAM 4 gb used)
Postgres 10 (RAM 2 gb used)
Windows MS 2016 Standart
Proc Xeon 2.4 G
RAM 8 gb
HDD 60 gb
users bonita 100
all processes 25 000
active processes 200
active tasks 200
Can you try to update to the latest version of Bonita available (currently 7.10.0) and see if you still reproduce the issue?
Since version 7.9.0 Bonita use a different transaction manager (Arjuna) and several improvement related to Engine performance has been done so there is a chance that the issue is now fixed.
As it turned out, postgres settings were in some places at the default level. We used pgtune and were able to improve the performance of Bonita - it would be nice if you added a link to pgtune https://pgtune.leopard.in.ua/#/ to the performance article.
We also upgraded the version of Bonit and Postgres to the latest versions, and also separated the database from the application.
After that, everything began to work great.
I have another question in the same context. During Bonita’s work with poor settings of the Database, we had a situation in which processes did not start (the http request was pending unchanged), and also when tasks were completed the next task did not appear and was in instantiation state (so we had 46 tasks accumulated) . After the reboot, everything worked.
Can you explain the reason?
Thanks for the tip regarding performance tuning with PostgreSQL configuration and PGTune website! I’ll try to update the documentation to include that as you suggest on performance tuning page (note: Bonita documentation is hosted on GitHub and pull requests are welcomed ).
When you said “During Bonita’s work with poor settings”, were you using Bonita version 7.8 or 7.9? A possible explanation was the lack of Bonita “workers” available. It can happen especially if you have connectors that took a long time to execute. This was improved in 7.9 (see 7.9 release notes and connectors documentation page).
Connectors wasn’t has long time. There is stopped on start/initiate. Maybe database has default low parameters as I sad on ticket.
at now all work is great.