Re: Large Degradation of IFS Performance through WindowsNetwork Neighborhood with V5R2 Upgrade

There is a new format for directory objects, called *TYPE2. Help text on this field, when displaying attributes of a driectory, says:

This directory is optimized for performance, size, and reliability compared to directories having the *TYPE1 format.

I don't remember is your directories are converted automatically - V4R5 would have been *TYPE1. And I don't know what the performance implications are. Could there be conversion issues? That will go away?

I see a couple PTFs (MF29296, in CUME 2344, and MF28857, in CUME 2211) that pertain to corrupted TYPE2 directories in V5R2.

There's a story <http://www.midrangeserver.com/tfh/tfh082902-story05.html> about the benefits, but it sounds like you know this already.

HTH

Vern

At 10:35 PM 2/10/03 -0500, you wrote:

We are troubleshooting a large degradation in throughput on IFS Performance in association with our upgrade from V4R5 to V5R2 this past weekend.

Our 3 TCP/IP Lines are verified as 100mbps and other overall lan throughput is not degraded. Packet loss is not an issue and respose time as reported through OPS Navigator is great. It just seems the iSeries Support for Windows Network Neighborhood is just not serving the data out the way it did on V4R5.

Upon bringing our iSeries 9406-740 back up after our upgrade, we first noticed the problem when we went to upgrade Client Access on workstations within our department. What used to take several minutes, now takes 15 minutes. A 20meg file is moving down in about 10 minutes.

I read that the IFS was supposed to be 'more robust' and more efficient in V5R2, we are seeing exactly the opposite.

Has anyone else encountered this issue with their V5R2 upgrade ?

William N. Harrell, Jr.
Cary, North Carolina 27511
wharrell@nc.rr.com