Forum Discussion
Performance is terrible
VasilMichev Hi
so today it is different loading is slower (I thought it was the Windows update that caused it), so it clarified.
As always thank you for the feedback, we did an update yesterday to add a whole load of new features to the community. Unfortunately, one of the changes caused a resource usage spike on the backend when we moved it to our Production environment. This led our engineers to throttle the community experience, which resulted in the errors you have seen.
I have been working with the engineers all day to fix the issue and we believe we are now recovering back to our usual speeds. I will be monitoring the community over the weekend to ensure there are no further issues.
Please accept my apology for any inconvienance.
- A1-A1Jan 29, 2022Gold Contributor
It's worth analyzing the profile synchronization, because I can now see on my dashboard, posts from the Excel Community (which I'm not in) so I think it's not indexing content correctly.
And instead of the latest (indexes the oldest posts)
- AllenJan 29, 2022Community ManagerHi,
Yeah we are aware of this, we will fix this as soon as possible.
Again my apologies
- HansVogelaarJan 29, 2022MVP
Before the update, applying a filter would be reflected in the URL, so
- One could bookmark a filtered list.
- Refreshing the page (F5) would preserve the filter.
Now, the URL is a generic URL that does not include the filter, so
- It is not possible anymore to bookmark a filtered list.
- Existing bookmarks with a filter don't work anymore - they time out.
- Refreshing the page loses the filter.
Also, the forum list used to display the most recent reply, now it displays the first reply, This is worthless if there are multiple replies.
This greatly reduces usability for me.
- VasilMichevJan 29, 2022MVP
Performance seems to be better today, however I get the following on each space:
- A1-A1Jan 30, 2022Gold Contributor
- AllenJan 30, 2022Community Manager
A1-A1 VasilMichev HansVogelaar
I can confirm this problem is persisting. We tried backing out the changes we made in the last release and still the problem exists so its obviously much deeper in our system than we thought.
We continue to work with engineers to resolve this issue and next update will be 8am PST on Monday, or earlier if appropriate.
Apologies in advance for the inconvenience