Please note that there will only be one client connecting to the web-server. I guess (if we can't get a separate dump machine), it would be better to dump on the client machine, than on the server machine where the disk will probably be active.
<br><br>OTOH, I'm not sure what kind of information would be interesting to us from a packet dump in this case?<br><br><div><span class="gmail_quote">On 12/7/06, <b class="gmail_sendername">Jeffrey C. Ollie</b> <<a href="mailto:jeff@ocjtech.us">
jeff@ocjtech.us</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On Thu, 2006-12-07 at 16:07 +0200, Ahmed Kamal wrote:<br>
><br>> - A kind of load monitoring tool we could/should use (other than<br>> "top")<br><br>If we could coordinate things with the crew at the hosting site, it<br>would be interesting to capture all of the packets between the server
<br>and clients during the test. There are some tools in wireshark that<br>would be useful for analyzing the results of the test. For best<br>performance you'd want to have a separate system capturing traffic that<br>was being mirrored by the switch. Second best would be to dump the
<br>packet captures to the web server's disk, but I would think that the I/O<br>caused by that would affect the test.<br><br>Jeff<br><br><br><br>_______________________________________________<br>Fedora-infrastructure-list mailing list
<br><a href="mailto:Fedora-infrastructure-list@redhat.com">Fedora-infrastructure-list@redhat.com</a><br><a href="https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list">https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
</a><br><br><br><br></blockquote></div><br>