Hello,
When forums.freebsd.org had a problem (with logs filling disk drive i think) I've noticed you are using varnish reverse http proxy. I've watched a video presentation by Poul-Henning Kamp, saying that 4 varnish servers replaced 12 or 14 squid server. This was interesting information regarding scalability.
It would be useful for all if we could have here on forum some tips regarind FreeBSD usage (and apps) in production environment.
More specific, how much hits/traffic will sustain a forum on a FreeBSD server backed by varnish. Or a software like Joomla. I know it depends on many factors (for example Joomla is more CPU intensive than Drupal) but still we can get an idea.
I know you probably use multiple servers for the forum. Do you do other optimisations other than varnish. Varnish help for caching, which improve hits per second, but do you use also traffic shaping?
I know maybe you might not want to disclose too much informations (security by obscurity) but even some ideas would help
regarding such a setup.
When forums.freebsd.org had a problem (with logs filling disk drive i think) I've noticed you are using varnish reverse http proxy. I've watched a video presentation by Poul-Henning Kamp, saying that 4 varnish servers replaced 12 or 14 squid server. This was interesting information regarding scalability.
It would be useful for all if we could have here on forum some tips regarind FreeBSD usage (and apps) in production environment.
More specific, how much hits/traffic will sustain a forum on a FreeBSD server backed by varnish. Or a software like Joomla. I know it depends on many factors (for example Joomla is more CPU intensive than Drupal) but still we can get an idea.
I know you probably use multiple servers for the forum. Do you do other optimisations other than varnish. Varnish help for caching, which improve hits per second, but do you use also traffic shaping?
I know maybe you might not want to disclose too much informations (security by obscurity) but even some ideas would help
regarding such a setup.