Performance issue with 1Password 7 on macOS

@MikeT -

1. Thanks for clarifying the code-reuse stuff. Minimizing code duplication is often a good software-engineering practice. You're additional info is helpful, thanks. With that, I propose we end this part of the discussion. Thanks again.

2. I'll advise when I've emailed you a diagnostics report. This seems helpful, thanks. I've got the ball and will post here (to this forum thread) once I've emailed per your instructions above.

~J

@brenty - thanks. Is there any means to accelerate this process of investigation + fix? 1Password is now effectively dragging my entire business down - because it's dragging me down. I use it 30+ times a day, and each time I log into a site, or even worse, make an edit, I can spend 20 minutes of dealing with the issues. It's horrible. Pls... help? How much money do you need to justify a top-level engineer focus on this? I'm very interested to figure out how to accelerate.

(I've not seen a human email reply from my diagnostics submission last night. Pls advise?)

@timlockridge - has anyone assisted you yet? (I don't work for AgileBits, but was just wondering.)

@timlockridge - got it. I'll work to tag you to stay informed with my progress. In the meantime: do you know of any additional means to get support? Thus far I only see https://support.1password.com/contact , which appears to be web-form submission, and I'm guessing gets me (or us) no further. I do recommend submitting per @MikeT's directions here.

I see downloads here for various 7.x versions, but nothing for 6.x. :|
https://app-updates.agilebits.com/product_history/OPM7

@timlockridge - initial performance experience for 1Password 6.8.9 (above) is MUCH better. It's early though.

AgileBits folks - one particular login entry in database of entries seems particularly problematic - even though it's way faster to work with in rev 6 vs rev 7, it's still relatively (to other entries) slower in rev 6 compared to other entries (in rev 6). But note: many other login entries were terribly slow in rev 7, so let's not be succumb to the temptation that "all of our problems are solved by removing a problematic login entry" -- because I doubt that's it. Even if it was, understanding how one entry (which is just data) causes problems like this is a significant issue unto itself.

For now, I intend to:
1. not use rev 7, and only use rev 6 for the foreseeable future.
2. "obsolete" the above, suspected problematic login entry. (I'll make sure not to completely destroy it.)

I realizing this (focusing on getting a working system over analyzing the original problem/symptoms) might divert from "analyzing problem root cause" for AgileBits (or whatever the company/organization is called that runs 1Password), and as a fellow engineer I feel for that team. For now, my team's basic productivity is my primary concern. Hopefully we can replicate and identify the problem later so that we can effectively employ long-term solutions.

Also: AgileBits, just for the record: I do not grant you access to my data. Hopefully you can not get to it, anyway. (If you can... that's an entirely bigger problem.) You've not requested access to my data, I'm simply being clear and proactive with my messaging.

Okay, after an hour-ish of rev 6, I'm more comfortable to report: 1Password 6.8.9 is a much better experience. No performance lags. The login item mentioned above that was recently created in rev 7.x is now trashed, and I avoid it. When I "touch" it again rev 6, performance does lag in rev 6 for a few seconds (it's in the trash, so I can't edit it), but as long as I stay away from said login entry, everything seems fine.

My current guess (and I want to emphasize there's major speculation in this statement): something got messed up when creating the above login-entry (it's for OpenTable.com, fwiw) yesterday with the 1Password data-server system, 1Password7 client is poor at managing server comm and/or data caching, and things just went bad. I can later get timestamps for the updates I made to said login entry, if AgileBits is interested--pls let me know. (For now, I've spent a lot of time debugging 1Password's stuff, and I need to get to other things.)

Also, my general user experience for rev 6 is waaaaaaay better than rev 7. It's like revisiting an old friend. It's snappy and minimal and just what I want. (Add the feature where 'Cmd-|' unconditionally pulls up the browser extension pop-up dialogue window, and I'd argue that for me it's perfect.) Rev 7 on the other hand always felt laggy and non-performant (even it was not taking 3 minutes to do basic operations, as noted above), and felt somewhat feature bloated. Rev 6 was great, and then I'm guessing some "UX wizard" at AgileBits decided to make a good thing "different"... and made rev 7. I'm not a fan. Pls bring back rev-6-like capability to the mainstream, and I'll be a much-happier user.

My procedure for downgrading to 1Password 6.8.9:

1. Quit rev 7. (I did not "remove"/delete anything, for better or worse.)
2. Install rev 6.8.9.
3. Open and run rev 6.8.9. (Rev 6 seems to have a different client-side "storage" mechanism--it appeared to take a few seconds to resync all the recent-since-I-upgraded-from-rev-6 item entries from the server/service/cloud/whatever.)
4. Remove Chrome, Firefox, Safari browser extensions. (I don't currently use other browsers.)
5. Reinstall #4. Browser extensions installs here.

Rev 6 download(s) here.

@timlockridge - my initial results are in: I have a much better experience with 1Password 6.8.9. Depending on your symptoms, you might want to consider downgrading and seeing if it helps you. Note: mine is NOT an official nor authoritative AgileBits directive. (I'm just a rogue user trying to make my 1Password environment usable again.)

My rev7-to-rev6 downgrade procedure, which includes download links.

@JohnnyUtahh Everytime you post to this thread it gets moved to the back of the queue. hth

All- until I experience problems with rev 6, I may be "signing off" from the forums. I might, at some point in the future, start a separate discussion about concerns for the 1Password service reliability over the long-term future, but that's another matter. For now, it seems (hopefully!) that my team's immediate, major problems are solved. If that changes I'll revisit things. In the meantime, I'm going to be very, very "slow" to adopt 1Password upgrades in the future, until AgileBits can demonstrate a rigorous testing/quality-assurance program. (That's quite hard to do in major software projects unless one has already built both a proactively-bought-in culture and a rigorous program to do this well. Retrofitting after the fact typically yields poor results. I'm not claiming AgileBits does or does not do this well. I'll let others ask their own questions and form their own speculations.)

As such, if I seem non-respondent on these forums it's because I've moved on to other business.

Additionally: there's a significant problem with the discussion-forum post editing feature that effectively turned my repeated edits of one, single post into many posts -- definitely not my intent. I'd appreciate if someone at AgileBits could delete these spurious posts. Thanks in advance.

Regards to all, and good luck with all your 1Password development and usage!

With my team's problem (hopefully!) solved by downgrading to rev 6, I'm signing off from the forums for now. If we run into further issues we may re-engage. In the meantime, we're going to be far "slower" to install version upgrades in the future, as we've grown suspicious (and from what we can tell, justifiably so) of the reliability of new, major-version releases.

I may or may not post a separate thread about larger, strategic matters related to 1Password, per results of this overall experience and what it might mean for the future. However, if y'all don't hear from me, it's not because I'm purposely ignoring you, it's just that I've (most likely) moved on to focus on other matters and I'm no longer following these forums. If AgileBits wants to reach me they can respond to my earlier email(s).

Regards to all, and good luck to the 1Password developers, users, and other stakeholders.
~J