Hi,
As can be seen in this screenshot. We deployed v13.4.0 today after upgrading from v13.1.0 and have noticed a significant increase in Redis server usage.
Is there something new in v13.4.0 that could explain the difference to v13.1.0. Is there something we should be looking at optimising.
We have a massive spike at deployment time which was around 1pm in the graph. We managed to get that stablised but are still seeing quite a lot more usage of Reids that we previously did.
Thanks Rick
5 Answer(s)
-
0
Hi rickfrankel
To find the exact cause of this performance issue, is one of the Social Login integrations active under Authentication in appsettings.json in your application? Is the
AllowSocialLoginSettingsPerTenantsetting also set to true? -
0
Hi @oguzhanagir,
The only login we have enabled in the appsettings.json is the JwtBearer login.
AllowSocialLoginSettingsPerTenant is also set to false.
Thanks
-
0
The one thing we do use is the Redis backplane for SignalR. Has something changed in that space?
We're seeing issues when we deploy as well with redis timeouts? We've never had this problem before.
-
0
In fact I remember now that the IOnlineClientStore has had its generic implementations removed and to upgrade from 13.1.0 to 13.4.0 we had to make changes to the code to make it work with the new implementations.
I suspect there has been some performance impacts introduced here that is causing our problems.
We have the chat hub disabled as we don't use chat, however we have our own application specific hub as well as the abpcommonhub.
Typically we'd have a lot of clients online as well (up to 2000).
-
0
Hi rickfrankel
Thank you for your feedback. We have created an issue regarding the Redis usage increase problem. You can follow the changes here.
