|
OK... I buy it. My calculations are a bit off, but here's the facts, so far anyway... At 3:30pm I started the GET command. Now it is 9:40pm and the file now contains 1,295,330kb. Facts or not, I'm guessing if I were to move the same file to the FTP share of this same PC and use another PC FTP client on this same network the throughput would be much better. History seems to prove my point around here and I'm just trying to find out why the IFS of the iSeries can't keep up with reality. FTP doesn't seem to be the only slow boat up the iSeries river. Simple drag and drop stuff is painfully slow as well and I've got three different iSeries boxes in-house and a long list of customer boxes to prove it. I suppose if you throw enough money into the iSeries box then it may start to compete with the throughput of some FTP freeware product on a $800 Dell or Gateway PC. This shouldn't, of course, be the case and I'm looking for an answer to justify the differences. If the platform is more stable but not fast enough to perform the task in an adequate time frame, then stability is a moot point. Ken Slaugh (707) 795-1512 x118 Chouinard & Myhre, Inc. CA/400 Certified Specialist iSeries Network/MSE Administrator http://www.cm-inc.com/ "Joe Pluta" <joepluta@xxxxxxxxxx To: "'Midrange Systems Technical Discussion'" ers.com> <midrange-l@xxxxxxxxxxxx> Sent by: cc: midrange-l-bounces@x Subject: RE: Why is the iSeries so slow idrange.com 08/12/2003 09:16 PM Please respond to Midrange Systems Technical Discussion > From: Ken.Slaugh@xxxxxxxxxx > > My current calculations result in a 4gig file taking 15 hours to FTP from > the iSeries to the PC client's hard drive. Is this for real? Are there any > tweaks to make this process more reasonable? Something ain't right there, hoss. You're throughput is well under 1MBit. A 4GB file is 32,000 megabits. (Note megabits, not megabytes). Divide that by 54,000 seconds (15 hours), and you get a throughput of about half a MBit/second. This does not compute, Will Robinson. Let's say you only have a 10MBit network. That means it should take (discounting ack/nak delays) roughly 3200 seconds, or a little under an hour to transfer 4GB. On a 100MBit network, you're talking a few minutes. Now, throw in some delays and normal network traffic, and things stretch out a little, but not that much. I regularly transfer hundreds of files between my iSeries and my network PCs using the MGET command of FTP. The most recent run included over 400 files totaling 2.5GB. On a non-dedicated 100MBit connection, even including the overhead for opening and closing 400 files, it still only took about 15 minutes, for a throughput of about 22MBit/sec. I don't know what's going on at your place, but it's not because the iSeries is "not capable of handling" FTP. Joe _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
