in-memory Repository server

We have some performance difference between our production env and our acceptance/develop server.
They only difference between these servers is that production uses postgres for the repository and acc/dev uses hsqldb for the repository.

[attachment=0]Screenshot 2020-09-24 at 08.09.46.png[/attachment]

We use a active solution aka war deployment.

EDIT:
Can it be that the hsqldb connect repository has negative effect on the overhall performance?

jeffrey.vandenhondel:
We have some performance difference between our production env and our acceptance/develop server.

Can you elaborate?
Also, was there a question? :)

Yeah i forgot to ask a question :P

jeffrey.vandenhondel:
Can it be that the hsqldb connect repository has negative effect on the overhall performance?

i would expect the opposite. that hsql which is purely in memory in he same vm without that it has to go over a network is way faster.

and if you use a active solution in side a war then the repository is also not that much used, its just for loading column info once.

Ok thank you. Then we will look further