First of all, you can have any number of Rugby servers running.

In your fastcgi script, you simply do a wait on tge fastcgi port. Upon
receiving a request you pass the data to a Rugby server (the actual
application). You use /deferred  in Rugby to achive this.

Now you return listening on the fastcgi port and periodically check if the
result has already arrived.

Two things can happen:
- You get a new fastcgi request. You do the same, but now on the next Rugby
server. Very simple load balancing but most of the time sufficient.
- You get the result. You write it out on the corresponding fastcgi accepted
port (that you saved in a block or so), close the port, and start listening
again.

So basically you use the fastcgi thing as a load balancer to the rugby
servers. As you use non-blocking deferred Rugby calls you have very fast
setup times (both on fastcgi and Rugby).


This is the picture:

------------
webserver
------------
fastcgi
--------------

Rugby    Rugby     Rugby


HTH,

Maarten





>
> > about the benchmarks....
> >
> > the 450/sec was Rugby. We will add fastcgi or lrwp, but we know we can
> scale
> > that up easily with some load balancing on the webserver side.
>
> Ah, probably so, although I am not sure if Apache itself provides it. I
was
> more interested in your Rugby setup. So it is clear, that in FastCGI
> scenario, user types some url, and your fastCGI script is called. What
does
> such script do - connects to your Rugby server? If so,. then how does
> webserver load balancing helps you, if your script connect to only one
> running Rugby server?
>
> -pekr-
>
> >
> > Although I know people were hoping that this was a FastCGI thing, it is
> > actually good news, as Rebol is performance wise good.
> >
> > --Maarten
> > --
> > To unsubscribe from this list, please send an email to
> > [EMAIL PROTECTED] with "unsubscribe" in the
> > subject, without the quotes.
>
> --
> To unsubscribe from this list, please send an email to
> [EMAIL PROTECTED] with "unsubscribe" in the
> subject, without the quotes.
>


-- 
To unsubscribe from this list, please send an email to
[EMAIL PROTECTED] with "unsubscribe" in the 
subject, without the quotes.

Reply via email to