Hi @jhoff33,
I took a look and odrive was doing its extensive initial scanning on startup. There is always a flurry of activity on startup as odrive checks every nook and cranny to make sure everything is as it should be. Generally I don’t expect it to be as long as you are seeing here unless the structure is extensive, but there can be other factors at play that can lengthen the time and impact.
In any case, it isn’t anything I would call “abnormal”. We run hot on startup, unfortunately. There was a post by another user regarding setting the priority of the odrive process. It’s not ideal, but it could help if you find that odrive slows other things down on startup: Decrease CPU priority so ODrive doesn’t interfere with other processes