I posted this on the railo google groups but thought I’d post again here:
We have a single instance of railo running on Ubuntu configured to use a
single context for around 200 websites. We use apache mod_proxy to forward
the requests for a specific domain to the corresponding subdirectory that
lives within the tomcat document root. For example, a request for
domain1.com gets forwarded by apache to {tomcat_root}/domain1.
This setup seemed to work well when we had less than 70-80 websites but is
starting to get bogged down now that we’re around 200 websites. We seem to
be getting a rather large constant latency (+3 seconds) regardless of load.
Has anyone seen similar results? Are we overly ambitious to expect decent
performance with this many sites on a server?
Have you done any profiling on Railo or Apache in an attempt to isolate the problem? Look at this blog post re Apache profiling:
I would look at your Apache config for possible problems with the numbers of threads and processes.
With Railo, you should be able to monitor the JVM using any number of available JVM monitoring tools. That could give you a sense of whether your performance issues have to do with Railo or Apache.On Apr 15, 2015, at 4:13 PM, Andy Jackson <@Andy_Jackson> wrote:
I posted this on the railo google groups but thought I’d post again here:
We have a single instance of railo running on Ubuntu configured to use a single context for around 200 websites. We use apache mod_proxy to forward the requests for a specific domain to the corresponding subdirectory that lives within the tomcat document root. For example, a request for domain1.com gets forwarded by apache to {tomcat_root}/domain1.
This setup seemed to work well when we had less than 70-80 websites but is starting to get bogged down now that we’re around 200 websites. We seem to be getting a rather large constant latency (+3 seconds) regardless of load. Has anyone seen similar results? Are we overly ambitious to expect decent performance with this many sites on a server?
–
You received this message because you are subscribed to the Google Groups “Lucee” group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/131a5f00-f792-488e-919f-a22344180dd2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Ok. So bone-headed mistake. The issue was that we had “Debugging” in the
railo admin turned on in production. Once we turned that off, we saw
dramatic increase in performance.
Thanks for all your suggestions!On Wednesday, April 15, 2015 at 4:13:25 PM UTC-7, Andy Jackson wrote:
I posted this on the railo google groups but thought I’d post again here:
We have a single instance of railo running on Ubuntu configured to use a
single context for around 200 websites. We use apache mod_proxy to forward
the requests for a specific domain to the corresponding subdirectory that
lives within the tomcat document root. For example, a request for
domain1.com gets forwarded by apache to {tomcat_root}/domain1.
This setup seemed to work well when we had less than 70-80 websites but is
starting to get bogged down now that we’re around 200 websites. We seem to
be getting a rather large constant latency (+3 seconds) regardless of load.
Has anyone seen similar results? Are we overly ambitious to expect decent
performance with this many sites on a server?