bullniom.blogg.se - october 2023

But these memory issues are still frequent and significant. One thing that did help was making sure none of my fonts were stored within a streamed folder. Somewhat less regularly, Drive will get up to 80%+ CPU and pretty much stall every other process on my computer. The simple act of browsing files within Finder has become a fairly tedious and time-consuming process. I would have though that by keeping my ongoing editing and saving only to those offline folders, I would mitigate any loading and resource-hogging that would normally occur from Drive's need to access/download/cache streamed files.įrequently, simply browsing through offline Drive folders and clicking on various files will have Drive at at least 30% CPU.

(Scare quotes because I'm not sure what "pausing" actually does, as I've tested it and I'm still able to access streamed folders which I haven't made available offline.)

I usually "pause" syncing during the bulk of the work day in the hopes that this mitigate any resource hogging on the part of Drive.

I only work within those current project folders that I've made available offline.

But I usually have ~5 current project and/or client folders that I've "made available offline" via the Drive desktop app.

I use it in streaming mode (I have 1.5TB of data in my Drive, comprised of mostly older client project files and various design assets).

Some quick context on how I use the Drive for Desktop app: Those purposes being frequent backup, storage, and cloud access of graphic design project files.Ī Drive Community thread I find extremely relatable here. If there were enough room, I would have chose the name "DriveAppSucksForMyPurposesAndComputer".

Hey Tom, appreciate the quick and thoughtful reply.