Lag on Finder when using odrive

Tony · June 29, 2018, 4:14pm

Hi @matt2,
This is definitely unexpected.

When you exit the odrive app, does the behavior stop? If not what if you exit the odrive app and disable the Finder extension in System Preferences -> Extensions?

Can you also tell me what version of MacOS you are running?
Are there any other extensions listed in System Preferences -> Extensions besides odrive?

matt2 · July 2, 2018, 9:08pm

Tony, if I do a complete uninstall of oDrive then Finder is fast again. I currently have it uninstalled on my MAC because I could not bear the latency but I will install it again and see if disabling the Finder extension fixes it. I am running MacOS 10.13.4.

As for other extensions I have one other called ‘Core Sync’ that is part of Adobe Creative Cloud (I think).

Matt

Tony · July 2, 2018, 11:03pm

Thanks @matt2.

I haven’t seen this behavior before, so I am hoping we can narrow it down by checking the Finder extensions and then going from there.

guillermo · July 13, 2018, 8:23am

Same issue here, when odrive is running finder slows down dramatically

matt2 · July 13, 2018, 2:46pm

Tony, just to follow up on this. I uninstall completely oDrive using the instructions you posted previously for uninstalling on a MAC and then reinstalled with the latest version and once it was done re-indexing all the files again then finder started going really slow again, so there was no change from the problem occurring previous to uninstalling and re-installing…

On the positive side, I did disable the extension as you suggested and that did speed up finder again and the lag was gone. However it is not usable without the extension so I had to re-enable it after confirming that the problem is in fact related to the extension.

Waiting your recommendations if you have any…

Matt

Tony · July 13, 2018, 3:37pm

Thanks @matt2,
I’m glad we’ve narrowed it down to the Finder extension. I am still unable to reproduce this behavior, so it must be specific to the environment and its interaction with the odrive extension.

Is there any difference when disabling all other Finder extensions and leaving only odrive enabled? I want to confirm its not some sort of conflicting extension behavior.

Do you experience this when clicking on any folder in Finder, or is it specific to only clicking on folders listed in the left-hand navigation pane, for example?

In the MacOS Activity Monitor, you will see one or more “odrive Finder Extension” processes.

When you observe this behavior in Finder, do you see a spike in CPU on any of the listed processes?
What is the idle CPU for these processes? Normal, idle behavior is between 0% and 0.5% CPU. This will vary a bit depending on the specs of the system.
What is the idle CPU for the odrive process? Normal idle behavior is between 0% and 2%. This will vary a bit depending on the specs of the system.
How many “odrive Finder Extension” processes are listed?

Do you have any other software installed that may be performing background operations or interacting with Finder that could play a part in this?

Tony · July 13, 2018, 3:38pm

Hi @guillermo,
Can you run through the same questions I posted above for Matt?

matt2 · July 13, 2018, 6:25pm

Tony,

No other extensions are enabled, just ‘driveapp’ which is your extension so it cannot be conflict of behavior.
All folders, whether I am drilling down in the right hand panel or selecting on on the left hand side. Doesnt even have to be a folder located in the oDrive root…
In activity monitor, Finder and oDrive processes jump to 100% or greater CPU when clicking a folder. I took a bunch of screenshots of Activity Monitor while Finder is “waiting” trying to open a folder so you can see the oDrive process, the oDrive extension process, and the Finder Processes under multiple scenarios opening a folder. There is only one oDrive extension process and one oDrive process.

Screenshots: https://www.odrive.com/s/40b797fa-3a2d-473b-9c0d-8b17f0d5f73c-5b48e7d9

I cannot think of any other software that would be conflicting. It happens all the time, even after reboot with no apps running. I thought it was a known problem because it happens on all three of my Macs (which is why I asked if it was fixed in oDrive2).

In “Login Items” the only background processes that launch when oDrive launches are “FlowSync” (for my Polar GPS running watch), “Android File Transfer Agent”, and “Vagrant Manager”. All three of those have been installed much longer than oDrive without problems with Finder and disabling them does not stop the oDrive issue so I doubt it is an interaction with them.

Tony · July 14, 2018, 12:09am

Hi @matt2,
Thanks for the information.

The memory and CPU are very high. Memory is exceedingly high for odrive and Finder, which is very unsual.

Can you send a diagnostic from the odrive menu so I can take a look at the client configuration?

Can you also give me an idea of how many objects (number of files and folders) is odrive currently tracking on your local system?

matt2 · July 17, 2018, 7:32pm

How do I send the diagnostic? and how do I get the total files and folder count?

Tony · July 18, 2018, 1:05am

Hi @matt2,
You can find the diagnostic option in the odrive menu (click on the odrive icon in the MacOS menubar).

That may be enough for me, for now. If not I’ll give you a couple of commands to run after I take a look.

prestonjohnlewis · July 21, 2018, 4:04am

Hi there, I’m having this exact same issue! Please help. I’ve also attached images of my high CPU usage. After I quit odrive, computer gets snappy and fast again like it’s new!

I love odrive and would love to keep using it but performance is killing my Macbook Pro. This has been happening for the last few months now.

Other details:

I primarily sync with Amazon Drive so not sure if that is impacting anything.
I’m running Mac 10.13.4

See attached screenshot.

prestonjohnlewis · July 21, 2018, 3:59am

It’s definitely an odrive issue, if I force quit odrive resources from Activity Monitor my computer gets snappy again, it’s like a brand new computer when I quit the odrive apps as far as performance goes.

I followed some instructions I found that had a terminal command and now the new version is showing (6413) but I am still having the same issue of lagging performance with finder and clicking almost any file spawns the beachball of death for a few seconds. Here are some screenshots of Activity Monitor. Apparently odrive is using 2gb of RAM and 158%+ of CPU! Crazy!

Please help.

Tony · July 22, 2018, 4:20pm

Hi @prestonjohnlewis,
Can you please send a diagnostic from the odrive menu and then ping me on this thread? I would like to take a closer look at your configuration.

matt2 · July 22, 2018, 4:40pm

Tony, did you get the diagnostics I sent you early last week?

Tony · July 22, 2018, 4:45pm

Hi @matt2,
Sorry, I didn’t see it. The diagnostics are only good for a couple of days, then purged. Can you please send another one (or two) and then ping this thread when you have so I know to look for it?

prestonjohnlewis · July 24, 2018, 2:06pm

Hi there! I just sent diagnostics.

matt2 · July 24, 2018, 7:47pm

Tony, I just sent my diagnostics.

Matt

Tony · July 24, 2018, 10:48pm

Hi @prestonjohnlewis and @matt2,
Thanks for sending those.

I took a look at the diagnostics and I the majority of what is being seen is due to the scale of the data. You both have between 650,000 and 700,000 objects that odrive is actively tracking both on the local and the remote side.

The more data that odrive has to track , the more overhead it will accumulateas it tries to maintain state on each object. This overhead will carry into pretty much every operation, including FinderExtension activity.

Unsyncing unused or little-used sections of data can mitigate this (the degree of help correlates to how much is removed from odrive’s scope). Is this an option?

matt2 · July 25, 2018, 3:51am

Possibly but is there any other solution? Does oDrive2 have better ability to handle that number of objects without lag? Why is it fast on windows oDrive but slow on Mac?

Matt