|
Although it *may* work, it will probably be death if you're talking a
significant load. If squid is URL rewriting, I don't immediately see why
you can't change the layout to what was previously suggested
(tv.blah.blah). That would work much nicer. You can do the rewrites with
apache2 as well, so another option would be to route the requests to the
apache cluster, and rewrite to go to tv.blah.com. This way the URL looks
like you want in the clients browser, and they get the right stuff.
> -----Original Message-----
> From: lvs-users-bounces+peterm=nypl.org@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:lvs-users-bounces+peterm=nypl.org@xxxxxxxxxxxxxxxxxxxxxx] On
> Behalf Of Erwan
> Sent: Friday, March 11, 2005 7:09 AM
> To: LinuxVirtualServer.org users mailing list.
> Subject: Re: High-performance Layer-7 switching in production
>
> I can't use this :
> http://sport.onedomain.com/sport/foot.php
> http://tv.onedomain.com/tv/mtv.jsp
> http://auto.onedomain.com/auto/audi.asp
>
> I must use this :
> http://www.onedomain.com/sport/foot.php
> http://www.onedomain.com/tv/mtv.jsp
> http://www.onedomain.com/auto/audi.asp
>
> - I'm using squid for reverse proxying with squidGuard URL switching but
> I've some limitations.
>
> With a Dual 3.2 Ghz, intel e1000, I can only handle 40 Mbps
> 1 of the 2 CPUs is always at 100% because of userspace/kernel switching
> The number of TCP connections saturate at 4000
>
> With squid URL rewriting, I'm testing this for my needs :
>
> |web1
> +----| SQUID1 |---+
+---URL:*/sport---
> -|web2
> | | |
> |web3
> | | |
> |web4
> | | |
> |web5
> | | |
> Internet ----| LVS |--|----| SQUID2 |---|----| LVS
|---+---URL:*/tv------
> -|web6
> | | |
> |web7
> | | |
> |web8
> | | |
> +----| SQUID3 |---+
+---URL:*/auto----
> -|web8
>
> |web9
>
>
> Perhahs apache2 is better than squid for this needs ?
>
> - Do someone has tried to use iptables layer 7 filter + lvs ?
> http://l7-filter.sourceforge.net/
>
>
> Regards,
>
> Erwan
>
>
> ----- Original Message -----
> From: "Malcolm Turnbull" <malcolm@xxxxxxxxxxxxxxxx>
> To: "LinuxVirtualServer.org users mailing list." <lvs-
> users@xxxxxxxxxxxxxxxxxxxxxx>
> Sent: Friday, March 11, 2005 10:48 AM
> Subject: Re: High-performance Layer-7 switching in production
>
>
> > The way of doing it at layer 4 is to use ip addresses i.e. : (surely
not
> > hard to get some more ips?)
> > But MAY require the app to be change'd slightly (normaly easier than
you
> > think.)
> >
> > http://sport.onedomain.com/sport/foot.php
> > http://tv.onedomain.com/tv/mtv.jsp
> > http://auto.onedomain.com/auto/audi.asp
> >
> > Layer 7 (i.e. a proxy NOT a router) will always be much slower than
> layer 4.
> > NB. As sugested you could use SQUID or Apache modules to proxy stuff
> (probably)
> >
> > As for performance of KTCPVS , I'm sure its pretty good.. just try it
> and see if it works for your needs.
> > You don't really believe commercial load balancer stats witout testing
> for your own environment do you? :-).
> >
> >
> >
> >
> >
> > Regards,
> >
> > Malcolm Turnbull.
> >
> > Loadbalancer.org Limited
> >
> >
> >
> >
> > _______________________________________________
> > LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> > Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> > or go to http://www.in-addr.de/mailman/listinfo/lvs-users
> >
> _______________________________________________
> LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> or go to http://www.in-addr.de/mailman/listinfo/lvs-users
|
