-
-
Notifications
You must be signed in to change notification settings - Fork 834
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fttb slow response time #3778
Comments
Please provide output of |
If I had to guess, it'd probably be due to the notification count attribute rather than loading of the notifications themselves |
I read all the notifications, but the response is still very slow. Only by delete all notifications, the server response will be faster |
I have yet to confirm, but this may be due to using |
Looking at the notifications logic, I don't see how this could happen, notifications are paginated, and loading the count is not a resource-intensive query. This could be a bad extension. |
I turned off all extensions and the problem still exists
|
Current Behavior
我發現了一個BUG,當我的通知數來到5000+,fttb時間會來到2秒以上,但如果我清除了所有通知,則會恢復到400MS
我的母語是中文,擔心使用翻譯軟體會有差異,所以在這裡附上中文說明
My native language is Chinese, I am worried that there will be differences when using translation software, so I attach a Chinese explanation here
I found a bug where the fttb (first time to byte) time would exceed 2 seconds when my notification count reached 10000+. However, if I cleared all notifications, the fttb time would return to 400ms.
Steps to Reproduce
Number of account notifications 5000+
Expected Behavior
Slow initial server response time
Screenshots
No response
Environment
Output of
php flarum info
Possible Solution
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: