×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I agree with you, Booth... 20+ minutes to write 50,000 rows? That's
slow to the point of absurdity. Something is wrong.
I also agree with Mike Crump -- using the IFS interface to write to
NetClient or serving out a file with NetServer will never be as fast as
a Windows server. However, 50,000 records taking 20+ minutes is more
than just being a little slower. It's ridiculously slow. My CISC
machine from 1993 wasn't THAT slow.
Something else is doing on here.
Booth, could you please clarify what is meant by "IFS" in all of your
statistics? Are you writing the file to /QNTC? Or the root file
system? When you say you're doing drag/drop to the desktop, where are
you dragging/dropping from? From NetServer on i5/OS? If so, what is
the underlying file system (the root file system?)
Booth Martin wrote:
The question that has arise is why is the IFS performance so terribly
slow?
We write a 50,000 row csv file to the IFS. We opened it with Excel.
20+ minutes.
We drag n dropped it to the desktop, 25 minutes.
We opened the desktop file with Excel. 22 seconds.
We drag n drop the desktop file to a Windows server. A few seconds.
We open the copy on the Windows server with Excel, 23 seconds.
The IFS is connected from a remote connection with a T1 line.
This mailing list archive is Copyright 1997-2024 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
