Oh! I’m not crazy 
I think there have been changes. Because if this request has always been present, there is another problem that has occurred, right?
I’m having trouble explaining this, but it’s true that something must have changed locally.
Perhaps a service recently added a bit too abruptly with the DB?
Possible, but it must spread the service… Because honestly, even 1 query per second shouldn’t block. Also check at the sequelize version level, etc., there may be issues at this level.
I’ll check if you want 
Well, it’s possible honestly, it’s true that so far the feedback from the gateway I had was that it was instant and almost invisible, and now suddenly you are four to complain, so I wouldn’t be surprised if there was a recent merge that introduces a performance issue!
Absolutely, if you look for any DB query in a service you need to check that it’s not called too frequently. You can put sequelize in log mode to see all the queries that pass.
That we need to update sequelize, but it’s a major and there are many changes, so it’s not a small project ^^
Yes I’m looking at that then
I have some good news to share with you! I’ve merged all the performance improvements on both Gladys local and Gladys Plus into the master branch. For users like @Terdious, I think the changes will be quite noticeable 
I just launched a dev build that will integrate all these performance improvements, and I’m curious to hear your feedback and your respective pings once it’s built.
If everything goes well after that, I’ll do a prod build on Monday!
For your information, the build is ready and I tested it at home: it works much faster!
Normally, if you test with your local instance on the dev tag + plus.gladysassistant.com, you should find a much lower ping, around 80-100ms. However, you will have to wait for the prod release (Monday if we don’t find anything this weekend) for you to see a ping around 50-60ms on plus.gladysassistant.com (I added a small client optimization so that the ping calculation is more realistic).
Do not hesitate if you see something that doesn’t work on the dev build!
Hello everyone!
The 4.0.7 update for Gladys is available, and includes all these performance improvements.
On my end, I’m getting much lower pings.
Your instances will update automatically within the next 24 hours if you do nothing.
Let me know if you see the difference!
150ms on PWA 4G
@VonOx Are you sure you’re running the latest version of the frontend? (Sometimes it takes 1-2 refreshes for the PWA to update)
To check, in the latest version the ping refreshes every 2 seconds without touching the page.
If that’s not the case, you need to do a proper hard-refresh
(Edit: I’m not entirely happy with this PWA update process either, we need to move to the latest version of Preact-CLI to benefit from their latest improvements, but so far we haven’t managed^^)
Ok, let’s start again ^^
In LAN:
Via Plus:
Nice!!
Well, that’s good, 60ms is what I also notice.
This is mainly « uncompressible » network time, because if you notice 24ms locally and 61ms remotely, that’s an additional 40ms for the round-trip, which doesn’t seem unreasonable
In terms of experience, does Gladys Plus seem pleasant to use with 60ms?
At first glance, yes it seems smoother.
I’ll tell you, I use it daily on mobile.
Hello @pierre-gilles,
Following the update, here is the local ping:
And the ping via Gladys Plus, which is significantly better than the 700 ms I had in the best case:
I will see with use if the error messages on the dashboard do not reappear. In any case, a better overall fluidity is felt remotely. Great job!
Thank you @Mastho for your message!
And do you no longer have the issue with the cameras not being loaded?
I will check if there are still optimization paths to do even better than 168ms, you never know there might be some small optimizations to take!
1283ms ?? That’s huge!
Are you sure you have the latest version of the front end and not a cached version? (See my message above)