mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-25 17:25:57 +03:00
[GH-ISSUE #2413] Editing of item takes a very long time to save #1254
Labels
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#1254
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ericlau-solid on GitHub (Apr 12, 2022).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2413
Hi,
Running this on a synology / docker config, and there were no issues, no updates, nothing. Today, when I make changes to one item, I notice that time to save is very slow (at least 15 seconds), when it used to be really quick.
I decided to pull latest docker and upgraded container, but no changes. The synology drive has lots of space, and no config changes had taken place. The only thing I can think of is size of data. Using sqlite so maybe that's becoming a problem?
@BlackDex commented on GitHub (Apr 12, 2022):
Please check the browser developer console (F12) and check the timings of the request.
It could be it is the client which takes a long time. You also mention you have a lot of items.
Could you tell us how many items there are in total in the databases?
You should be able to see some numbers within the
/admininterface.@ericlau-solid commented on GitHub (Apr 12, 2022):
Hi,
The system is working normally now, which I have no explanation. I do wonder if timing is an issue, since I rebooted both NAS, docker, container, multiple times. I was about to give up, went out for lunch, and now all is well.
Next time this happens I will definitely open browser console and check timings. Thanks.