Skip to content

Conversation

@earocorn
Copy link

@earocorn earocorn commented Jan 4, 2026

Small configuration change that allows for higher thread pool size of CSAPI service, to better handle large amounts of transactions. We are allowed to configure this to be higher because CSAPI request handling is almost entirely I/O bound.

@alexrobin
Copy link
Member

Did increasing the pool size help with your issue in the end?



@DisplayInfo(label="Thread Pool Size", desc="Number of threads used by the service to handle incoming requests")
public int threadPoolSize = Runtime.getRuntime().availableProcessors();
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe it would be better to default to the number of available processors when this is set to a special value (like 0) instead of setting it directly in the config (+ update the desc annotation to document this)

…mber of processors in CSAPI service module
@earocorn
Copy link
Author

earocorn commented Jan 7, 2026

I believe it should work a lot better in an upcoming event in which we need to ingest a lot of video streams. I don't currently have the time to implement the "distributed" obs store (with multiple MV store), but will also work toward that change. Also, I have made the change to keep the config file clean

@alexrobin alexrobin merged commit 6a1efc5 into opensensorhub:master Jan 8, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants