Speed concerns
For ages now, 1Password has suffered from inexplicable slowness. Here are some examples.
On the cli, the op tool takes 2 seconds to return a record. I've seen it take up to 5.
❯ hyperfine --warmup 3 "op read 'op://infra/example/password'"
Benchmark 1: op read 'op://infra/example/password'
Time (mean ± σ): 1.925 s ± 0.043 s [User: 0.095 s, System: 0.039 s]
Range (min … max): 1.865 s … 1.987 s 10 runs
In the browser, fetching and filling passwords is quick. But saving or updating a record is very slow. This used to be way worse, so bad that I thought it was crashing (30sec) but now its 'just' 4-12 seconds. This is across all browsers I've tried.
I'm on an M2 MBP, system resources are abundant. I'm on a reasonably fast gigabit net connection thats not contested. Presumably 1P shouldnt require anything other than read/writing to its local db for these ops, at worse some encryption/decryption. In the browser I suspect it just talks directly to the cloud but since it tends to require the local app to be installed it must be talking to it, over a socket or something? Its a modern machine with typical nvme speeds, so its not IO bound. I can't see any contention for resources in any sort of monitor (activity monitor, bottom, htop, btop, istat menus etc).
Executing the cli (just for ease of profiling) and analysing what its doing:
It seems to spend relatively little cpu time, about 100ms. Most of which it spends decrypting the vault, makes sense. What doesnt make sense is the 2 seconds it spends just kind of doing not much at all between various ops. It doesnt actually even get to the part of opening the vault until 1.3 seconds in, so its spending a lot of time... initialising?
I'm using a token to authenticate, so its not sitting there waiting for my touchid or similar.
The desktop app is responsive and fast otherwise.
1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Browser: Not Provided
Comments
-
i have noticed similar issues with timing. I opened another thread about the idea of being able to have the CLI use the local datastore. not just for timing, but other reasons. i am on m1 mac with 1gig connection and my testing of the latency has been within 10ms out to 1password.
1
