Arjun Sivakumar
unread,Oct 3, 2025, 2:47:49 AMOct 3Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Nussknacker
Hi team,
I’ve been exploring how to control the thread pool size in Nussknacker request-response scenarios. From the official documentation, I didn’t find a clear reference about the number of threads used (e.g., “the server runs with X threads”).
I tried two approaches in `application-customizations.conf`:
**Case 1**
"request-response-embedded" {
engine: "lite"
deploymentConfig {
restServer {
port: 8181
thread-pool {
min-threads = 4
max-threads = 16
queue-size = 200
}
}
}
}
**Case 2**
scenarioTypes {
"request-response" {
deploymentConfig {
tasksCount: 4
}
}
}
In both cases, after adjusting the thread numbers and checking TPS, I observed no difference—the TPS remained the same.
**My question:**
1. Is there a configuration available to control the thread pool and memory for request-response scenarios?
2. If yes, could you please guide me on the right way to configure it?
3. If not, how is the thread pool internally managed in request-response mode?
I am using community edition of Nussknacker of version 1.18.0
Thanks in Advance,
Arjun S