-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Very slow multiple add/delete operations #4693
Comments
Hmm, i thought we fixed that already in |
Also, there is a similar issue #4669. |
It is slower without enabled push also. |
In my case I don't have any delay for single operations. Only for multiple. |
I can't really reproduce your findings (with the
edit: even with 499 items it's 1.7-2 seconds for these requests. |
It's my log. What diagnostic could I do?
|
Try to enable |
Okay, I can only reproduce the issue if I enable push. |
Attached delete logs with enabled push. |
This is emptying bin trace with disabled push. |
Subject of the issue
I installed Vaultwarden and Bitwarden Unified Beta for testing and comparing.
Both are installed as Docker containers on the same Debian VM(It is 8 cores Intel Xeon with 4GB RAM. So it is not a slow server).
Both vaults use a shared Postgresql installed on the same VM as Docker container.
Both vaults are empty before testing.
Both are behind the same Nginx proxy installed on the router.
I use the web vault, the Firefox official Bitwarden extension and the Android official Bitwarden app.
The clients and the servers are in the same LAN.
For a testing purpose I exported 427 passwords from Firefox to CSV.
I imported and after some pause deleted these items. After that I emptied the recycle bin.
I tried to import from web vaults and a Firefox extension - the results were the same, so I guess it is not a client issue.
Deleting and recycle bin emptying are possible only from the web vaults.
The results are in the table below.
When testing Vaultwarden with enabled push notifications it was difficult to measure the times precise because of web vault 60s timeout errors. Besides, after these timeouts the data in the Vaultwarden web vault stopped to refresh and it needed to renew the page and to unlock the vault.
Deployment environment
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden:
Install method: Docker
Clients used:
web vault, firefox extension
Reverse proxy and version:
nginx/1.26.1 installed on the router
MySQL/MariaDB or PostgreSQL version:
PostgreSQL 16.3 (Debian 16.3-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
Steps to reproduce
Expected behaviour
Vaultwarden and Bitwarden should work at approximately the same speed.
Actual behaviour
Vaultwarden is much slower than Bitwarden particularly with enabled push notifications.
Troubleshooting data
The text was updated successfully, but these errors were encountered: