Signing back into the Community for the first time? You'll need to reset your password to access your account. Find out more.
Forum Discussion
System
4 years agoSuper Contributor
Electron
This discussion was created from comments split from: 1PW8 for macOS.
Former Member
4 years agoI've just check 1PW 7 for comparison and it used 109 MB of RAM and utilized only 5 threads. This is with two different accounts (business & private), inside them dozens of vaults with a bit over 2000 entries, in total. In addition the 1PW 7 built-in Safari extension consumed only 17.5 MB RAM in total (1Password Extension Helper + 1Password (Safari)) and used 8 threads. Adding these two ends up in 126.5 MB RAM and 13 threads in total.
On the very same Mac 1PW 8 consumes over 215 MB of RAM and uses overall 63 threads during the first start, when there was not a single account added to the app, meaning that it only showed the "Welcome to 1Password - Sign In" dialog and nothing else. After adding my two accounts to the app, the memory consumption has been raised to 275 MB, while the thread count did not changed noticeably. The new 1Password Safari extension (v2.0.6) consumes 176 MB of RAM and using 7 threads. These ends up together in 451 MB RAM and 70 threads in total.
But apart from the memory usage and the thread count, the overall performance feels sluggish at best on my late 2019 MacBook Pro 16, when running natively under macOS 11.5.1. From time to time spins up the fans of my Mac, while the 1Password app end up in the top of the most energy consuming apps in the Activity Monitor. Moreover trying it out in a macOS 12 VM in Parallels, the performance is simply unbearable. I had to wait around 3 to 5 seconds(!) to see any reaction in the app when clicking on an entry in the list, even after several app restart, and OS restart, when nothing else has been running. I'm not sure what's happening in this case, but 1PW 7 performed well in the same VM.