spread[logd] scalability
"BUSTARRET, Jean-Francois" <[email protected]> Wed, 9 Jul 2003 17:41:47 +0200
| Newsgroups | gmane.comp.apache.mod-log-spread.user |
|---|---|
| Message-ID | <30884B45CCC6714B800F6F294BEC0A990163307B@MSGEXS11.tf1.groupetf1.fr> |
This is a multi-part message in MIME format. ------_=_NextPart_001_01C34630.9B42B8B2 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I am looking for a way to handle 5000+ req/s on 100+ serveurs. = mod_log_spread looks like exactly the tool I need to handle this kind of = task, but I am a little bit concerned about scalability. I did a quick & dirty test with 1 web server + 1 logger & 2 web servers = + 1 logger. Web servers & logger are on different subnets, using = multicast, with the multicast ttl changed in data_link.c. Multicast = should be working : spmonitor reports 0 unicast retransmits. With 1 web server, spreadlogd wrote about about 260 lines/s, and about = 370 with 2 web servers. Each web server was handling about 400 req/s. How does spread & spreadlogd scale ? What would be the limit of spread & = spreadlogd ? Jean-Fran=E7ois Bustarret eTF1 - Internet Architect [email protected] ------_=_NextPart_001_01C34630.9B42B8B2 Content-Type: text/x-vcard; name="BUSTARRET, Jean-Francois.vcf" Content-Transfer-Encoding: base64 Content-Description: BUSTARRET, Jean-Francois.vcf Content-Disposition: attachment; filename="BUSTARRET, Jean-Francois.vcf" QkVHSU46VkNBUkQNClZFUlNJT046Mi4xDQpOOkJVU1RBUlJFVDtKZWFuLUZyYW5jb2lzDQpGTjpC VVNUQVJSRVQsIEplYW4tRnJhbmNvaXMNCk9SRzplLVRGMQ0KRU1BSUw7UFJFRjtJTlRFUk5FVDpK RkJVU1RBUlJFVEB0ZjEuZnINClJFVjoyMDAyMDQwMlQxMzUxNDlaDQpFTkQ6VkNBUkQNCg== ------_=_NextPart_001_01C34630.9B42B8B2--