High CPU usage in Google Drive File Stream (Opus and Explorer)

Help & Support
1

I'm using Google Drive File Stream with my G Suite account.
I've tried to figure out why D/O uses 30%~40% CPU even when there's no active task.
The CPU usage increased and stayed at around 40% when I opened 4~5 docx/pptx.
When I quit D/O, the CPU usage decreased.

Is it a known issue?

2

What happens if you do the same thing, with the same files/folders, in File Explorer instead of Opus?

3

CPU goes down shortly.
It's interesting to see the CPU usage is stuck at 35% when I open a file via File Explorer while D/O is running. Once I quit D/O, the usage goes down to 8%.

4

Which process is using the CPU when you do that?

5

Google Drive File Stream.

6

So doing something in File Explorer causes Google Drive File Stream to use lots of CPU but you think Opus is involved in some way?

It sounds more like a bug in Google Drive File Stream so far.

Edit: Below only works in Opus Pro, so may not be useful as a test if using Light:

You could try setting Preferences / Miscellaneous / Advanced: [Troubleshooting] no_external_change_notify = False in Opus to see if something Opus is doing in reaction to external changes is triggering a request to GDFS that makes it use lots of CPU. But even then, the bug would be something GDFS is doing. (Be sure to set it back to True after testing, as it will prevent Opus reacting to a lot of filesystem events.)