-
Notifications
You must be signed in to change notification settings - Fork 145
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
New version of bridge fetches huge amount of data #243
Comments
yes, this is very much by design - Bridge now stores encrypted message bodies to be able to serve them to the client faster. yes, you can switch this off - go to Settings/Advanced settings/Local cache - you can disable it there. |
Ah, and I see it's |
This does seem to be an issue (MacOS 12, Bridge 2.1.1), I was just doing an initial setup/sync of my ~600MB account and Bridge has downloaded over 20GB since it began. Here we can see it's downloaded just over 2GB since I restarted the process :
In a log file spanning just one hour, there are GETs for the same items repeated many times over and over :
|
I tried disabling the cache and re-syncing from scratch, but it didn't make any difference, still ridiculous amounts of data downloaded and Apple Mail was struggling to send even a single email, and selecting an un-synced email would often simply timeout. I've now reverted to Bridge v1.8.12 where this behaviour doesn't seem to exist (almost fully synced and just 1.2GB of data in total, vs the 20GB+ previously), and the end user experience with Apple Mail is far more responsive. Checking the logs over a similar hour long period of syncing as before, indicates that v1.8.12 is requesting a GETs of unique items an order of magnitude less often.
|
reopening this as we're investigating. we were assuming the excessive traffic comes from client-side, but are now confirming this theory. will keep you posted. |
Thanks @andrzejsza, let me know if I can gather any logs, etc to help. |
+1
|
we've completely change the behavior with Bridge v3. closing the issue, it anyone still experiencing unreasonably high network traffic - please get in touch with support for further debugging. |
When launching proton-bridge at 27e7d79, it now fetches a huge amount of data on start - logs suggest it's downloading every message and storing it on disk.
Expected Behavior
I'm already using bridge to download messages to this machine - there's no need for bridge to store an additional copy.
Current Behavior
Since what I'm guessing is 6bd0739, hundreds of megs of encrypted blobs are fetched and stored in ~/.config/protonmail
Possible Solution
If, as it seems, this is intentional, maybe an option to turn it off? Otherwise it seems like this is going to eat as much disk as one has quota in protonmail.
Steps to Reproduce
Version Information
27e7d79 (looks like this will become 2.0.1). It presumably happened earlier, but it's hard to test.
Context (Environment)
Linux, built from git, running headless. Email is pulled over IMAP for use with another client. This is a single machine setup, so the other client stores a copy and so does bridge.
Detailed Description
I'd like bridge to not store all this on disk, but as it seems intentional, perhaps an option to turn this behavior off?
Possible Implementation
I don't write Go and am not very familiar with the tree, sorry.
The text was updated successfully, but these errors were encountered: