What effect does changing the teiid-async thread pool have?
Issue
- is 20 a reasonable value for the
max-threadsfor theteiid-async? - Could it affect negatively to any other process?
- Based on the logs it looks like worker threads (are created) on the fly to delegate query execution to the actual datasource using the translator. So is the thread pool used for the I/O threads and they create new worker threads to do the actual work?
- how does the thread pool affect performance
- does it become a bottleneck in web applications?
- what will be the optimal configuration of the thread pool?
Environment
- Red Hat JBoss Data Virtualization 6.2
async-thread-pool- Thread Pool to be used with Asynchronous operations in Teiid
unbounded-queue-thread-poolas defined injboss-as-threads_1_0.xsdjboss-as-threads_1_1.xsd
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
