@dandelany noticed high CPU usage on the sequencing server, even during idle periods. This seems to be caused by a development-related watcher process used when developing the sequencing server.
To address this, I set the default values in the Docker Compose to match deployment which makes the CPU utilization normal. If you specifically need to develop using the sequencing server and hook up a debugger within the ide, you can uncomment the necessary sections in the Docker Compose configuration file.
Additionally, I exposed the knobs to the sequencing server in the deployment Docker Compose as they were missing.
Verification
There is now very low CPU usage in a development environment.
Description
@dandelany noticed high CPU usage on the sequencing server, even during idle periods. This seems to be caused by a development-related watcher process used when developing the sequencing server.
To address this, I set the default values in the Docker Compose to match
deploymentwhich makes the CPU utilization normal. If you specifically need to develop using the sequencing server and hook up a debugger within the ide, you can uncomment the necessary sections in the Docker Compose configuration file.Additionally, I exposed the knobs to the sequencing server in the deployment Docker Compose as they were missing.
Verification
There is now very low CPU usage in a development environment.