|
To answer everyone's questions:
1. I have 60 VS with 2 RS each, plus another 60 VS with 1 RS each. (If
possible, I would prefer not to discuss why I have 60 VS with only 1 RS
each right now. Suffice it to say that there are reasons. It's two
different applications with 2 different purposes.)
2. When I asked about the throughput measurement, I meant HOW to obtain
that measurement. I know we're looking for packets per second, I just
don't know the best way to obtain that. There's no snmp on this
computer. All the counters I can find show totals for packets in and
out, but not pps. I was hoping to get away without showing my ignorance.
Too late. :0)
3. No need to explain why NAT works the CPU harder. That much I
understand.
4. The health check interval is 2 seconds. The 60 VS with 2 RS each are
checking via http. The other 60 VS with 1 RS each check by tcp connect.
Let me know if I missed any.
--
Eric Robinson
-----Original Message-----
From: lvs-users-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:lvs-users-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Fernanda
G Weiden
Sent: Friday, October 31, 2008 3:56 PM
To: LinuxVirtualServer.org users mailing list.
Cc: Horms
Subject: Re: [lvs-users] Are LVS / ldirectord Multithreaded?
I meant backend check, not external..
2008/10/31 Fernanda G Weiden <fernanda@xxxxxxxxxxxxxxxxx>:
> 2008/10/31 Joseph Mack NA3T <jmack@xxxxxxxx>:
>> Horms is 50% CPU right for ldirectord on a heavily loaded (lots of
>> packets) 2.5GHz LVS director?
>
> Using multiple processes for different vips would help to isolate the
> problem, at least. Maybe there is a weird external check or something
> killing the machine.
>
> --
> Free Software Foundation Europe
> Join FSFE's fellowship today! - http://fsfe.org
>
--
Free Software Foundation Europe
Join FSFE's fellowship today! - http://fsfe.org
Disclaimer - October 31, 2008
This email and any files transmitted with it are confidential and intended
solely for LinuxVirtualServer.org users mailing list.,Horms. If you are not the
named addressee you should not disseminate, distribute, copy or alter this
email. Any views or opinions presented in this email are solely those of the
author and might not represent those of . Warning: Although has taken
reasonable precautions to ensure no viruses are present in this email, the
company cannot accept responsibility for any loss or damage arising from the
use of this email or attachments.
This disclaimer was added by Policy Patrol: http://www.policypatrol.com/
|
