Hi @Jess1,
The number of odrive extension processes relates to how Finder’s extension framework works. Finder, itself, will load a few instances as default behavior for the Finder app. Additional extension instances are created when Finder is used within other applications, as well.
For example, if you open a file browser within the TextEdit app (File->open), a new odrive Finder Extension process will be run for that Finder instance that was created. If you close TextEdit, then that process should be terminated within a minute or two. Finder tends to keep these processes around longer it seems it should, sometimes. odrive doesn’t perform the actual loading and unloading, so it doesn’t have a say in how Finder is doing this through the framework. This same behavior can be seen with lots of other applications that happen to load a Finder instance, so you can end up seeing a a number of odrive Finder extension processes pop-up.
To uninstall odrive completely, you can follow the instructions here: How do I uninstall odrive?
Without an uninstall, if you exit odrive and uncheck the odrive extension in System Preferences -> Extensions, you should also see the odrive Finder extension processes go away after a little bit.
For the sluggishness you are seeing, this is probably just a side-effect of having so much data exposed. odrive has to work very hard to keep all of that data in sync, so there will be quite a bit of overhead. The amount of overhead is directly related to the amount of data that odrive has to keep track of. Are you actually exposing billions of files locally, or you working with a subset of that?