
Maybe once a week or so, Drive will momentarily disconnect, causing the following issues: I have a steady fiber internet connection and have eliminated my network/wifi as the cause. Tangentially, another frequent issue is Drive's tendency to randomly disconnect. Maybe just due to the nature of the Drive app and how it works VS the old Backup and Sync, the only solution for my workflow is storing all current projects in local folders and moving to Drive when complete/ready for backup. I have not tried working online all the time as I imagine that would only make these issues worse. PSDs that are 100mb+, potentially up to 750mb. Generally I am working on relatively large files. Interesting, that at least does give me hope that there's some way to configure this to a point where my whole system isn't being lagged up. Now it seems my system and/or workflow is just incompatible with the Drive desktop app, or at least to the extent that it doesn't slow down my whole work day. Before the forced transition from Backup & Sync, I had 0 issues with my trusted Macbook and workflow. Now, my Macbook is fairly old at this point (new M1 is on the way), but I can directly attribute a general lagginess and slowness to the Drive desktop app. 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.
#YOUTUBE SNL TRUMP PRESS CONFERENCE OFFLINE#
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.



