LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

Re: Release new code: Scheduler for distributed caching

To: Thomas Proell <Thomas.Proell@xxxxxxxxxx>
Subject: Re: Release new code: Scheduler for distributed caching
Cc: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
From: "Matthew S. Crocker" <matthew@xxxxxxxxxxx>
Date: Fri, 27 Oct 2000 11:26:19 -0400 (EDT)
On Fri, 27 Oct 2000, Thomas Proell wrote:

> 
> 
> On Thu, 26 Oct 2000, Matthew S. Crocker wrote:
> 
> > Why can't we come up with an API the Real Servers can use to tell the
> > ldirector their load so the ldirector can update its routing table?  It
> 
> Sounds simple, yes. Write it! :-)
> 
> Writing kernel code is hard, and not many people have the experience
> and the time to do a good job, even if it WAS simple.
> 
> Moreover, my scheduler was developed as the topic of my master-thesis.
> So, there were also other (maybe academic/theoretic) issues, that 
> were considered. For example that the client doesn't have to install
> some extra software (what may speed up the stuff). Another point
> was, that the CACHES don't have to have extra software.

I'm not talking about rewriting schedulers or kernel modules.  I think we
need an API for applications so they (because they are the only ones that
know their true load) can express that load in a numerical way to the
directors.  The directors can also have a weighting system because a very
busy fast server can still be a better choice than a non-busy slow server.

No changes to the scheduler or kernel needed.  Just a way to update the
LVS routing table every 5 seconds or so with better load information so a
scheduler can make better decisions.

-Matt
 
-- ----------------------------------------------------------------------
Matthew S. Crocker 
Vice President / Internet Division         Email: matthew@xxxxxxxxxxx
Crocker Communications                     Phone: (413) 587-3350
PO BOX 710                                 Fax:   (413) 587-3352
Greenfield, MA 01302-0710                  http://www.crocker.com
----------------------------------------------------------------------



<Prev in Thread] Current Thread [Next in Thread>