RE: IFS response time-additional information

Increase your buffers, say double.  I am running 16384 for both send and
receive.  What are your ethernet line configurations?  Check the MTU.  I am
running 1496 bytes on both ethernet cards.  Are you running ethernet, token
ring?  What is the MTU's on all the routers between the client and the
server?  What is the MTU on the firewall?  Again what is the run priority of
the Netserver job(s),qzlsfile and qzlsserver.  Both have a runpty of 20 with
a time slice of 3000 on my 720, single processor.  File transfers are fast
but not as fast as pc file servers.  Though we do have some 300 interactive
users pounding the system.

Good Luck,

Chris Bipes

-----Original Message-----
From: Reeve Fritchman [mailto:reeve@ltl400.com]
Sent: Monday, December 17, 2001 7:17 PM
To: Midrange-L@Midrange. Com
Subject: IFS response time-additional information


This is a multi-part message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Additional information:
(1)        I'm running through a WAN, not a LAN.
(2)        My Internet circuit into the iBox is a partial T1 (128K).
(3)        QSYSWRK was in *BASE (Chris B., thanks for your sharing your
expertise so often); I've moved it into one of my shared pools previously
set up for QCMN, etc.
(4)        TCP/IP send/receive buffer sizes are 8192.
(5)        I'm accessing HTML files in a directory off the root level of the
IFS (not QDLS) using NetServer/file shares/mapped network drives.
(6)        Response sucks regardless, Notepad or HTML editor.
(7)        VPN doesn't seem to affect response.
(8)        Our workload on the WAN and iBox is low.