It’s Cybersecurity Awareness Month! Join our interactive training session, or learn about security and AI from 1Password experts.
Forum Discussion
ddribin
2 years agoNew Contributor
"op read" is pretty slow, ~700ms per invocation
Hi all,
I've noticed that op read is pretty slow, taking on the order of 700ms per invocation. Here's a benchmark using the https://github.com/sharkdp/hyperfine tool:
% hyperfine --warmup...
robxyz
9 months agoNew Contributor
I ran into this issue as well only after trying to run ansible playbooks against groups or hosts. Seemed a bit slow but worked without error on 1 or 2 hosts but 5 or more I was getting intermittent errors and extremely slow playbook runs. Errors were intermittent as well showing one of two 'ansible.errors.AnsibleLookupError' logs:
Unable to sign in to 1Password. Missing required parameters: username, master_password, subdomain, secret_key.
or
connecting to desktop app: connecting to desktop app timed out, make sure it is installed, running and CLI integration is enabled
When I increased the forks to 10 or 20 from the default 5 in ansible (the amount of parallel sessions it runs) the error popped up immediately and not a single host would gather facts.
I'm leaving all these details as I think it is related to this issue as the more hosts / frequent the op
requests are it seems the slower / more likely to block from the desktop app side.
It does make op
unusable though for ansible and any kind of long playbook or against large groups of hosts unless using the op connect methods which don't resolve the inventory lookups on each task but aren't convenient at all to integrate into exists ansible scripts / roles.