Welcome to ProjeQtOr new Forum. We migrated old forum to the new website.
You will find all your posts here, with your usual account.
Just one point : you’ll have to reinitialize your password. Use “Lost password” feature.
Hello,
I am still experiencing performance issues with ProjeQtor.
After moving the instance and database to localhost, there has been a noticeable improvement, but I still notice slowness with certain actions, particularly “saveObject.php.”
For example, changing the number of days for a task on my server results in a 32-second wait! Whereas if I compare it with the ProjeQtor demo, it takes less than 7 seconds.
How can I optimize this, please?
EDIT: ProjeQtor with PHP8.4-fpm, apache2 and PostgreSQL 17 on debian 13, 4 CPU, 8GO ram
Thanks,
Best regards,
Florian
“Be a yardstick of quality. Some people aren't used to an environment where excellence is expected.” ~ Steve Jobs
"...and while some may see them as the crazy ones, we see genius, because the ones who are crazy enough to think that they can change the world, are the ones who do." ~ Think Different
Hi,
The "long" part is not the save, it is the replan of the project planning.
You can try and disable automatic planning, then manually execute planning when all changes are done.
Hi,
No, it's not the replan. After disable it it's the same time.
And we can see in Firefox that is "saveObject" which is take too much time.
Or maybe i do not the good action to disable it ? How ?
“Be a yardstick of quality. Some people aren't used to an environment where excellence is expected.” ~ Steve Jobs
"...and while some may see them as the crazy ones, we see genius, because the ones who are crazy enough to think that they can change the world, are the ones who do." ~ Think Different
I think you have an issue with the configuration of your server.
33 seconds to save an objet, 2,8 seconds (on server side) to display it : it is much too long.
For the save latency, if you enabled the module "Budget on Organization", try and disable it.
We know it brings some latency on saving.
We have a ticket on this side to bring an major improvement (delay consolidation to unsynchronize it from save)
But just read 2,8 seconds, it is much too long.
I am working on an assistance for a client that has read delay of about 1,8 seconds, which is too long.
The dealy is due to large amount of resources (several hundreds).
We'll bring an quick improvement on this specific side, but in your case, except if you have thouthands of resources, you should not have so long read time.
Either your CPUs are slow, of your configuration is not correct on PHP or MySql side.