Chrome extension slow after migrating to encrypted metadata

Community Feedback
1

Ever since I enabled encrypted metadata the Chrome extension is painfully slow, sometimes taking 2 - 3 minutes to load my passwords. It’s virtually unusable at this point. I should also mention that when I open the Passbolt workspace in my browser, it’s also quite slow, though not nearly as bad as the Chrome extension. The workspace takes like 15 - 30 seconds to display my passwords. I have 3,886 passwords stored.

2

Thanks for creating a new thread @SoBeGuy . Can you tell us about:

  • What kind of machine do you have locally (CPU/memory)?
  • Is the majority of the resources shared or personal or a mix?
  • What kind of key do you use (RSA3072 or 4096)?
  • Do you see any error in the browser extension console?

Thank you for helping us investigate this issue.

3

It happens on all my Macs, for example M4 with 32 GB. 99% of the passwords are personal. My team users aren’t having any issues, I guess because they each only have a few passwords stored. The key is RSA 3072. There are no errors in the console.

4

That shouldn’t take that much time with these specs, can you send us a message at support@passbolt.com mentioning this thread, we can organize a call with the browser extension developers see what’s up. Cheers,

6

Hi everyone,

I have the same problem with the firefox plugin. 40 seconds to see my secrets for 541 secrets.

I use the community edition 5.2.0 on a vps with 16 cores and nvme disk.

7

Follow-up on the performance issue. With the introduction of encrypted metadata, a performance cache layer was implemented. However, it appears that this caching mechanism is not functioning correctly in your case. There could be multiple reasons for this, but the core issue is that the cached information fails validation.

The team is currently working on a fix that will make the cache mechanism self-healing when invalid data is detected. This fix is scheduled for the v5.3.x series.

In the meantime, if you need an immediate workaround, you can manually truncate the contents of the metadata_session_keys table in the database. The first connection will reinitialize the cache, and performance should improve.

8

Thanks for the info!