-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Owen,
Please do not top-post. I have re-ordered your post to be bottom-post. On 8/11/17 10:12 PM, Owen Rubel wrote: > On Fri, Aug 11, 2017 at 5:58 PM, <christop...@baus.net> wrote: > >>> Hi All, >>> >>> I'm looking for a way (or a tool) in Tomcat to associate >>> threads with endpoints. >> >> It isn't clear to me why this would be necessary. Threads should >> be allocated on demand to individual requests. If one route sees >> more traffic, then it should automatically be allocated more >> threads. This could starve some requests if the maximum number of >> threads had been allocated to a lessor used route, while >> available threads went unused for more commonly used route. > > Absolutely but it could ramp up more threads as needed. > > I base the logic on neuron and neuralTransmitters. When neurons > talk to each other, they send back neural transmitters to enforce > that pathway. > > If we could do the same through threads by adding additional > threads for endpoints that receive more traffic vs those which do > not, it would enforce better and faster communication on those > paths.> The current way Tomcat does it is not dynamic and it just > applies to ALL pathways equally which is not efficient. How would this improve efficiency at all? There is nothing inherently "showy" or "edity" about a particular thread; each request-processing thread is indistinguishable from any other. I don't believe there is a way to improve the situation even if "per-endpoint" (whatever that would mean) threads were a possibility. What would you attach to a thread that would make it any better at editing records? Or deleting them? - -chris -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlmOi2YACgkQHPApP6U8 pFh+ohAAkIDqAaZK3mmQsSAE100a4RMwCyAjT076eiEkqj3MVJHUBuYf2adNlRYe jvcKJCmvu061mW+/kos0+YIrt6ao2j60+fryX1goMOXhBxxrSlioccOwLkBu4HIG SB/AuFIYqIG6S1ICqVunCFJsrYnMuJEX6WfA8O7G+sQWFH54w9XadewabEduu3uO PwoP14a7XFOC8RPp9HM9Rdx8EfADRXrFugN0E5YSjXN5cdMs8bxJcabo8vjVnfNH JDCkvF0tDd+FWj4t/AqXugM6fc6EYb8sSxEifxkdbu701A4doe8n1d1zawd3+qd4 IBVR6jFDHGqRm6cHvmhI8G4Tlx6c5EX29ZGTTdKnPvNloyob0a3/LauPJMr/97Xv eIsj0shEfbUOWgcBWHRMbXbmZRjOAU7wxXtm2KsLZpJ6ZVZe9c7wSRLThYjp0Yyx jgpwHN4sVPGG821trGht29E3v1e2GN1A7nuYbM7A7BK1PHP3MmLozVxAMxAip1T4 hVaVDHc1hd/G79Jvugq/T7atKQfOetLD4vg9ZFGIukaPZwA+3BtMYTNWn/bX2u9d hBsWCw5Abn1SABlQ4cl87OJF9jya4p/P3Kqejyg9jbDbUy9J21QFEP6n5qHy9/vy Jg6cjWpho6s9Ajx690ZNsdudDPoRuBe2TRLkFTOnUXsgwHTmToY= =tiO+ -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
