I have just set it to 256MB, 10 iterations and 16 parallellism. No noticeable lag, well, it takes about 3 to 5 seconds to login depending on the device. I can live with that…
2 Likes
@Sophia Do all your devices use Bitwarden’s mobile client for Android?
3 Likes
@grb I tested this on my Fold 4 (both in the browser and the app), the Chrome extension and the Windows Store app.
1 Like
Currently, only the mobile clients (and CLI) make use of the parallelism feature, so you should notice a significant reduction in the unlock/login time on the android phone.
1 Like
Using IOS 16.3.1 and I have set my argon2 settings to 110 mb, 10 iterations and 8 paralism. Not noticeable effect on IOS, so I can’t event see any longer loading time compared to pbkdf.
I might try to adjust it a bit up, but don’t quite know what aspect to adjust higher. Got to do some more reading to learn more about best possible setup.
2 Likes
Can you use auto fill with it?
Edit: with the 110 MB setting
2 Likes
I expected that, but it unlocks in about 5 seconds, tops. I guess the Galaxy Fold is just that fast?
2 Likes
The mobile apps use a different implementation of the Argon2id, which can run the hashing calculations in parallel, thus causing a speed increase by dividing the calculations between multiple cores. The other apps (browser extensions, desktop) have a an Argon2id implementation that uses WebAssembly, which unfortunately doesn’t support parallelization. Thus, if you have set parallelism to 16, your Android mobile app should be about 16 times faster than a browser extension.
3 Likes
When will the 2023.2.0 Android app be available on Google Play Store?
The Chrome extension and Mac App Store clients have both been updated to 2023.2.0, but not the Google Play Store 
1 Like
Be mindfull of the fact that changing the Parallelism will change the output of the algorithm i.e. the resulting hash?
It does in this test page Argon2 in browser and other ref sources.
Therefore I would expect that all clients will need to be using the same value.
1 Like
Nor the Firefox extension (Mozilla store?)
2 Likes
Thanks for that. So here’s a noob question: am I correct in assuming that higher values mean better security from hackers?
No…? Your device must support 16 threads for that, so for mobile devices anything over 6-8 doesn‘t make sense as I don‘t think there are any phones with 20 threads.
The Snapdragon 8 Gen 2 has for example „only“ 8 threads.
2 Likes
Memory yes, iterations yes but I honestly don‘t know about parallelization and as far as this forum goes, no one really knows* what the impact of that is. Leave it therefore at 4 or reduce it if you want.
*I‘ve seen multiple threads about this question and no one was able to give a satisfying answer.
3 Likes
Yes i am using auto fill with it, by the means that I press the line where it comes up with suggestions for password and auto fill it to the site. I am using biometric to unlock my vault, so I am actually not logging in to my vault each time I need to a website. By that way I don’t really experience anything from the decryption that is happening, since my local vault on iOS is encrypted based on my iOS setting.
Hopefully this answers your questions.
2 Likes
I think I know why that happens. I think iOS secure enclave stores the account encryption key and therefore skips the whole part about running the master password through a KDF.
I‘ll test it out with far higher numbers for fun. If my assumption is correct, you should be able to go up to 1 GB without any problems in most cases.
Edit: I made a new post in the forum. The memory limit in iOS does not apply to Bitwarden if you use biometric unlock.
FYI - I know this a bit off course for comparison: I use 1 GB on my LUKS2 using Argon2id running 25000 iterations (plus a 45 character password) and the unlock/open is around 10 seconds. Of course the container is fully quick after being opened and I have a bunch of extra RAM on this machine.
Like others here I am waiting for FF to get the BW extension updated for testing.
1 Like
As long as “testing users” have a good backup/export of their vault then you will never be fully locked out. Merely a small hassle to restore the vault from scratch in about 5-10 minutes max. If I don’t break things once in a while I am being just too conservative for my lifestyle, LOL!
Yes, keepass has been around a long time, but certainly not for 35 years. Maths hurt you 2023 subtracted by 2002 is equivalent to 21 years. 
Yes, it is really slow in coming through.
I am starting to wonder if BW have actually submitted it.