Wireshark Deciphering

Daniel teletautala at gmail.com
Mon Mar 12 13:38:53 MDT 2007

I have used curl to grab the file.  It is close to the same time as if
I were to refresh the page (<1sec.).  The problem I am having is when
I go from one php script to the following.  I believe it may not be
the network, but I am thinking there needs to be a tweek on the
server.  I need help with that.


On 3/8/07, Levi Pearson <levi at cold.org> wrote:
> Daniel <teletautala at gmail.com> writes:
> >
> > Problem:
> > The directory on the iSeries consistently takes a fraction of a second
> > to come up.  The one native on the Linux box takes from 2 - 12 seconds
> > to load.
> > I captured 94 packets for the one on the Linux box and 35 packets for
> > the one on the iSeries.
> >
> > Question:
> > Why would there be such a discrepancy?  Is there something I can
> > change on the Linux box? Apache?
> I don't have time now to look at wireshark files, but if the same data
> ends up getting transferred, I don't think it's likely that variations
> in the number of packets that get transmitted will account for the
> speed difference.  Things like tcp window size, etc. can break tcp
> streams up in different locations.  You might try running a wget or
> something locally on the Linux box to confirm that the delay is not in
> the network.
>                 --Levi
> /*
> PLUG: http://plug.org, #utah on irc.freenode.net
> Unsubscribe: http://plug.org/mailman/options/plug
> Don't fear the penguin.
> */

More information about the PLUG mailing list