Server performance with Curator Tool
We are testing the connection and performance between GGCE(2023.8) and Curator Tool. Everything is working fine, however we have some doubts about the GGCE performance.
We have now for earch GGCE Server instance 12GB of memory, 1GB for each GGCE Web container and 6GB for the database (Express Edition)
To load 28136 records, the server takes half an hour to save them. According to statistics, there was no significant impact on the servers during the test.
This is the highest point:
We consider that it is a long time given that it was the only test done at that time
Questions
- Has GGCE limitations for the coneccion with Curator Tool?
- If above is true. Could we configure that behavior?
- In production (with 32GB) this process takes just 1 minute or less. I know there is a big difference. Will GGCE has a similar performance that our current GGCE Classic services with 32GB?