Why limit the number of threads in a Queue?
Resources: Less threads means less memory and less cycles. Competition: Threads, whether operating system threads or logical threads, compete with each other within a Tymeac Queue, with other threads in Java , and with other processes in the Box. Sometimes adding more threads slows down overall processing because of resource limits, (memory, cycle, network, locks, blocking, etc.) Let’s say you have an application that uses two (2) additional threads such as the prior example. In an n-tier application server you may have one hundred (100) of these applications active at one time. That means that there are two hundred (200) threads for these applications competing with each other for resources. Now the same application with Tymeac. You set up a Tymeac Queue for each database access component. For this example we set ten (10) as the maximum number of threads for each Queue. When one hundred (100) applications are active, the maximum number of threads for these processes is twenty (20), no
