I can't really classify whether my code is good or bad because I don't have a reference for what constitutes 'good' code. For the first stable release, I want to focus on optimizing what I can and improving the responsiveness of the controller under high stress. Currently, all actions in the main tick loop are blocking, and Rocket accesses resources from a separate request thread pool. This means that responses to gRPC requests should be fast, but the tick loop itself is quite slow. For example, when starting 10 units, each start requires 10 network requests, which are processed sequentially. This becomes an issue only when all units are started on a single driver. My goal is to have a controller that's fast, with clean and efficient code.
I can't really classify whether my code is good or bad because I don't have a reference for what constitutes 'good' code. For the first stable release, I want to focus on optimizing what I can and improving the responsiveness of the controller under high stress. Currently, all actions in the main tick loop are blocking, and Rocket accesses resources from a separate request thread pool. This means that responses to gRPC requests should be fast, but the tick loop itself is quite slow. For example, when starting 10 units, each start requires 10 network requests, which are processed sequentially. This becomes an issue only when all units are started on a single driver. My goal is to have a controller that's fast, with clean and efficient code.