I'm not sure that your method is very useful for two: 1) Your mileage will vary massively depending on the link bandwidth/latency, and also how congested it is 2) There's an awful lot of overhead when using Windows SMB to move files around, so you won't get a 'true' measure of bandwidth
You'd have less impact on the line, and get more accurate results, if you could poll the router via SNMP and get interface statistics. Is this an option for you? You could get a measure of latency by testing, and graphing, ping times across the link. P. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Eric Logeson > Sent: 24 May 2005 16:28 > To: [email protected] > Subject: Measure bandwidth > > Hello List > > I wanted to get some basic bandwidth statistics across a WAN > link. The approach I think I am going to take is the following: > Use a perl scipt to read in a bunch of files, determine the > sizes, start a timer (not sure how to do this yet), copy the > files across the link (winxp->win2003 server), stop the timer, > and finally write out the bytes/sec metric to a log file. I > planned on scheduling the perl script to run every hour or so > for a week. > > Are there modules of interest for this project. Any > suggestions on the approach? > > > Thanks > Eric > ***************************************************************** Gloucester Research Limited believes the information provided herein is reliable. While every care has been taken to ensure accuracy, the information is furnished to the recipients with no warranty as to the completeness and accuracy of its contents and on condition that any errors or omissions shall not be made the basis for any claim, demand or cause for action. ***************************************************************** _______________________________________________ Perl-Win32-Users mailing list [email protected] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
