|
Hello,
Sorry. What I meant by session is "https session". But my question was
answered in
http://marc.theaimsgroup.com/?l=linux-virtual-server&m=103169281103492&w=2,
which states:
----------------------------------------------------------------------------------------------------------------
there is an issue with the current persistence handling when RS weight is set
to 0: new connections can be scheduled to "stopped" RS if "affinity" for this
client exists. It is good for setups that prefer to serve even new
connections from client that finishes its session (multiple connections) to
the stopped RS.
----------------------------------------------------------------------------------------------------------------
Yes I've read that and I agree with it. I simply didn't put 2 and 2
toghether ;)
I do not think that there is a problem with one director and LVS-DR
performance-wise. Could you give us more specific numbers on how big the
http pages are, which are being fetched and if those 10000 clients all come
at once or if there is an expected distribution.
I'm currently projecting around 10000 clients coming all at once (although I
can set them to come at different times, I would rather have 3 or more
directors, just in case). Those http requests are php scripts that might
What case are you referring to? 10000 clients with LVS-DR is not even
worth mentioning when we talk about performance, it's a rounding error
of the estimated amount of concurrent connections :).
(not always) do an upload or download of at most 1MB.
So you have 10000 clients calling a PHP script which in return feeds
back 1MB worth of data every ten minutes, 24/7, right?
How fast is the Internet link?
Best regards,
Roberto Nibali, ratz
--
echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq'|dc
|
