> To the Chris, I personally don't think it is the norm since your average > site usually don't get that kind of load. I would start with 2 or 3 and > scale up as needed.
I have gotten request to separate traffic to multiple ports so that Network Engineer can manage/debug network traffic easier (by port). I totally agree this will make troubleshooting easier, but I am also afraid there is performance cost in implementing this. < Chris, I think it is fair to say each connector instance will take up < a finite amount of computing resources so the more you have < they will push the server towards its upper limit. Whatever that < might be depends on CPU speed and RAM. < The tomcat instance could get very busy some times with only 1 connector. (3k+ requests every minute) Therefore, I am wondering once I starts having 20 connectors (listening on 20 different ports), will the performance be affected by a lot. < Well 3000 / 60 is 50 requests per second. If you know how long < it takes to service a request then you are in a better position to < tackle the performance issue. < < Let's assume, conservatively, your server can do 10 per second. < Then having the load balancer with 5 workers (linked to 5 connectors) < should cover your situation. So having 20 might be a bit excessive at < this point. < < Note that workers don't have to link to a local tomcat. If you find < that your server is maxing out, you can add another server to scale up < further. < < Long < www.edgesoft.ca < --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
