-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Erick,
On 10/14/18 00:03, Erick Erickson wrote: > Can we stick to the question? Which is "what advantages Tomcat > might bring to be worth the _very_ significant effort it would take > to replace Jetty, assuming that it's a choice between the two". I just read that someone is building an alpha SPNEGO implementation for Solr. Tomcat ships with one. That might be one item in its favor. Given that most servlet containers are nominally equivalent, I'm not sure I could build a compelling case for why you *should* switch to Tomcat. But given that there is an opportunity to re-evaluate the container you will use (e.g. if you switch from container-hosted Solr to Solr-hosted container), then switching becomes easier should you choose to switch. The decision to move to Tomcat may be made simply to prefer a product with a clean AL2 license (Jetty has restrictions; I haven't read them but I suspect they are not really problematic in any meaningful way). > For the level of effort required to make the switch to Tomcat, I > suspect the consensus would be to use neither and switch to Netty > or similar, which makes the discussion so far pretty much a waste > of electrons. So, if you think switching to Netty will be worth it, I'd like to know *those* reasons. Netty is a great product, but you only benefit if you abandon the servlet spec and build to their non-standard APIs. That would basically require a ground-up rebuild of Solr from scratch in order to gain any perceivable benefit from switching to Netty. If you guys would like to see some independent performance evaluations, have a look at this: https://www.javacodegeeks.com/2016/05/benchmarking-high-concurrency-http - -servers-jvm.html Skip to the graphs. They are nearly impossible to read, but show that all servers benchmarked seem to have roughly the same performance characteristics. Basically, you can't go wrong. Anything that might seriously impact your performance will come down to resources (hardware) or configuration (e.g. if you want fast TLS, don't use the Java crypto provider). I know there are some throughput-vs-CPU-usage numbers around for Tomcat versus httpd and one of two other servers/configurations. I'm trying to dig those up. Thanks, - -chris > Erick On Sat, Oct 13, 2018 at 6:24 PM Christopher Schultz > <[email protected]> wrote: >> > Martin, > > Wow, wild conjecture with no supporting evidence. Seems like par > for the course with you. Read on, if you dare. > > On 10/13/18 13:41, Martin Gainty wrote: >>>> >>>> ------------------------------------------------------------------- - --- >> >> >>>> - --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] For >> additional commands, e-mail: [email protected] >> > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/ iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlvInIUACgkQHPApP6U8 pFh0JQ/+J53IZkbqdKnWLa4ndg8v2AZrhrWha0YHSMlOih9k7ANcw+0G0jtTek6m l2CTgQOuKGGn3/PVfP6OypEXOhQ2XR/VQBrUCZzKzLIlEcEEiyLV0vb9fm4HnmIR KwEsgU0pnTIwsE540F8eP/MK5AqQ2ULqMlsX+m19U0/RAx6PnXQGGxAORRIVLFi/ mK7Yu1Ou2pbT/3W1iL63fbbkmDgyeRqo6lthWvwa2Q+zAq/qe/N4drJ1dAYdSg4c L6xY5JVVYFRlS2+2Cc0TeBNB3yVsRPakz4Q4P+GKyTOS61yuXsPL/DhDpLdHqca9 WkRrG0MBVPM9X7HRd7PrNvzJIyeEJYFLOEt7UFrZ/tmMlmZD5M5w33L4na2ZJN86 MKxcCQz3M/FySfbaKmrRBu8BAIkCmmU7DAMdGUCLJKQ3sdHknc7QisLARrY0Xx17 nDjXcKxu0lrO6ZTKJ1/nHwGZz1tEe+cgJKwcEyTWlFnYm1IS0A9FlMHdePvA54Jh x1J4cW7qut5ir1WS3Un7K52RndGGXNVTfkyTsJnCx9+65Wuq86M+lgEuyiRCuhVL wUpCx2l3qNcTCOZjUj+i8cq1aJIEm+Ql7EeS9JEB4Y+2yCOhgPS9lKotTTLmVFbK 2ccG9nyMu8iPN2UPyT+VqN+9HmXZ/FVQj2lTfU02lAlWZODxu88= =tcIz -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
