-
Notifications
You must be signed in to change notification settings - Fork 137
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
Delay fetching notes via API #589
Comments
I can confirm this. However, I don't know when this was introduced. Recently, I did some work in order to improve the speed, see #525 (Notes app 3.5.0). I remember, that I measured a time of around 200ms for API requests. However, I don't remember the exact Nextcloud server version. I think it was something in 18. Now, with Nextcloud server 19 and Notes 3.6.3, I get something around 2.200 ms. Hence, we have to investigate in which version of Nextcloud server or the Notes app the slowness was introduced. I did a quick test on this using Nextcloud's docker images, but I couldn't find any difference between versions. Any help is appreciated, since it seems to be a time consuming investigation. |
Oh, and you can safely ignore the session error message. It's a bug in Nextcloud server (see nextcloud/server#20490) which was fixed in nextcloud/server#22243 (will be part of 19.0.2). |
There are similar delays when using webdav so the problem may be more general. |
Interestingly, I can't see a delay anymore, when using the Android App. However, when doing a request using Does the problem still occurs to you with the latest server version? |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
In practice, I can't see any delay since a long time. I'll close this issue for now. If it will happen again, we can re-open it. |
Describe the bug
When I fetch a note (or note information) using the API, there seems to be a 2-3 second delay. This is consistent, independent of server load, so it may indicate some internal time-out
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Output within a reasonable amount of time. Since this is a lightly loaded server on a local LAN I'd expect a response in milliseconds.
Server (please complete the following information):
Client (please complete the following information):
Log files
A message similar to this is written to the NC log for each request:
The text was updated successfully, but these errors were encountered: