Save process is extremely slow

[auanasgheps]

Hey there, I'm a long long time user of this plugin, thanks for making it.

I would like to know if you can control how saving is performed, because currently is not optimal, or it's a KeePass thing.

In a normal situation, my 500kb database on Google Drive takes 6 second to save. My upload speed should make it instantaneous, but I can still deal with this. However when the connection is pretty bad like when travelling or some unexpected stuff happens, saving can take minutes. If it fails due to timeout or disconnection is the same, takes ages. The main problem is the app is unavailable to the user during this time frame.

Is there a way to save the DB in the background without halting the app and bothering the user? Like using cache and then upload the cache later on?

[ghost]

I guess Keepass does this. When saving normally also same issue.

[auanasgheps]

Not in my case, when I save locally it is instantaneous. It does lock up the app but really is just a fraction of a second

[auanasgheps]

Hi, this is a gentle bump to see if anyone else is seeing this. I've also tested beta 2.0 but nothing has changed.

[auanasgheps]

Bump. Anyone?

[NexRX]

I'm expericing this too right now.

[auanasgheps]

Bumping for the last time, I think this plugin has been abandoned.

[NexRX]

I've been experiencing this to, if the project is no longer maintained, maybe it's forking time?

[Kyrodan]

Hi together, I'm still watching all the issues. And I still use my own plugin daily. I am willing to fix issues, but for quite a long period I haven't had time to do these fixes.

From my point of view we have two options:

• everyone can fork this repository and develop it's own plugin
• I would accept co-maintainer to fix issues

Answering your intentional question: KeeAnywhere was designed for immediate online access (without usage of the cloud's desktop client). So with poor/bad internet connection we have to wait for a timeout first. As an additional option I implemented the local "caching" of databases for "offline" scenarios. As conclusion I currently don't see an option to improve this behavior in this Plugin. Maybe you can use KeePassOneDriveSync which has another intention: save locally and sync to cloud afterwards. Maybe this sync is async nowadays - you have to check this.

Regards, Daniel

[auanasgheps]

Hi @Kyrodan, thanks for your reply.

With my current setup, your plugin locks up KeePass from 8 to 15 seconds when saving a change to a DB on Google Drive.

This happens using an excellent internet connection, on bad/instable connectivity the issue is even worse, waiting for 30+ seconds.

I have tested KPSync for Google Drive, is super fast and it has a different approach: it saves the DB locally (locking up KeePass for a fraction of a second), then uploads the file to Drive in background without locking up the app.

For my usecase, the downside of that plugin is I have to manually download the DB first, whilst with your plugin I can pick it from KeePass directly.

Would you consider this approach?