so you can check to see how long it's taking.
And, generally, anything, you know, over let's say,
forty or fifty milliseconds to post something is probably
not very good depending on your connection. That was also another consideration.
So one of the other tools that we were looking at before we, we closed out this session was
And I'll pull this up now...
was other tools that you can use to validate
specifically, what is being done and what pages are being done?
So, there's tools out there that will allow you
to, you know, pull down the entire cascading style sheet.
There's things that will allow you to accelerate your, your service
so you're not pulling down a ton of little packets.
There's things that can be done to accelerate this,
to reduce the amount of gets.
So, there's things that can be done to increase the performance here.
But just in Wireshark, the realm of wireshark
if you want to look at the actual data and check out and see what's happening here
you can validate from one step to the next exactly how long it's taking with timestamps.
So, it's important to understand timestamps.
It's something that will help you when you're troubleshooting because
as an example, let's say, you're looking at a transaction from a client to a server.
One of the things that you could do is
run a Wireshark capture at the client, like we did here.
If you have access, you can run one at the server
and you can do a compare.
And take a look to see exactly what's going on within a specific set of time
so that you can see where the hang up might be
or where the performance hit may be.
We were talking again about that performance hit.
One of the key things that we were discussing
and we were talking about, one of this I posted in the forum, was that
IO is a big thing. So if you're, let's say, you have a disc drive on the local server
wherein the read-write times are poor
that will potentially show as slow performance when you're accessing a website
if it's, if the system doesn't have enough memory.
If the NIC card is having an issue, let's say, it's not on a gig
and it's on a fast ethernet and you see a lot of problems
where it's actually buffering that traffic.
There's a lot of things that you would look at to see
specifically if you had a performance issue outside.
But this in Wireshark, this example is one of those things
where you may be able to get an understanding of where you need to look.
So as we had mentioned before, if you see long periods of time
or you see tons of get requests, it might be something where
it's just not able to provide you the paging time or it's sending way too much traffic
and you're not getting it back in time.
So, those are some of the things that you can check.
Not only capturing it in Wireshark and giving you clues to where to look
but specifically, do you have a problem with a client?
Do you have a problem on the server?
You know, do you have problem in between on the network?