jbertram commented on PR #6027: URL: https://github.com/apache/activemq-artemis/pull/6027#issuecomment-3499685641
> ...for me it's not about "needing" the extra performance, it's about having the option. Why would you want to have the option if you don't need the extra performance (assuming the main use-case here really is related to performance)? > I'm not sure what you mean by statistically significant differences... I mean a meaningful, measurable difference for a real-world use-case. For example, 10% faster average load times for the web console using the default configuration, 20% faster load times for the web console in high-load uses-cases (e.g. lots of addresses & queues), etc. Something like a 2-3% increase probably isn't worth the additional complexity (i.e. technical debt) here. > I'm sure a number of cases could be made for decoupling messaging traffic from web traffic, and for security. What kind of decoupling did you have in mind? Messaging traffic is handled via Netty by the Core broker which is already separate from web traffic, which is handled by the embedded Jetty instance. Both use independent thread pools. Also, traffic for each goes over different ports and potentially even different network interfaces. Can you elaborate on the security aspect here? > We're probably looking at this from very different perspectives :) That's certainly possible. Since you specifically [solicited opinions in the description of the Jira](https://issues.apache.org/jira/browse/ARTEMIS-5745) I figured I'd jump in. I'm always trying to better understand how folks use the broker, and I'm not super familiar with Unix domain sockets so I'm keen to learn about the use-case here. Aside from that I'd like to reduce complexity and technical debt where it makes sense. I don't want to fall into [premature optimization](https://www.geeksforgeeks.org/software-engineering/premature-optimization/). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information, visit: https://activemq.apache.org/contact
