Stories
Slash Boxes
Comments

Slash Open Source Project

This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login
Loading... please wait.
  • LVS is a great system, and works _extremely_ well.
    For best scalability you are best advised to use a VS-DR - direct routing, since this allows the servers to reply directly to the clients. (just make sure you switch off ARPing on the private interfaces or you'll get massive headaches)

    Also I'd also use IP based client persistance since that way you'll make running the service much simpler. Other things - journalling FS? How will you share data between servers? Replication? NFS? Database server? etc...

    I know of a location using LVS to serve ~100 million HTTP requests per day, all load balanced using LVS, so you can be sure LVS will scale :-)