| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: Crappy Windows 2000/XP UDP performance |
From: "Geo"
Try it with a bigger file, 200 meg can fit in disk cache.
Geo.
"Scott" wrote in message
news:429620a3$1{at}w3.nls.net...
> Just as an onlooker:
>
> I have a new mailserver with a 500 PIII Xeon and a gig Hawkings adapter
> plugged into a Netgear 752 stackable with a couple of gig ports. The
> other gig port goes to my dell poweredge 1500.
>
> Using a small file (dripping sarcasm) like Server 2003 SP1 (200+megs) I
> get a sustained throughput in the 120mb/second; 12% saturation. I'm
> guessing i'm coming up on the Xeon's ability to make the push as it's
> almost pegged on taskmanager (about 98%)
>
> Scott
>
>
> Mike '/m' wrote:
> > On Sun, 22 May 2005 12:19:08 -0400, "Frank Haber"
> > wrote:
> >
> >
> >>I'm amazed, too (at 12-13MBps). Can you run a perf meter on both ends,
next
> >>time you transfer a file? I'd be interested in how long the CPU pins
(g).
> >>(Not that we can differentiate a PCI bus throttle from a CPU clot from a
> >>bridge running out of interrupt time.)
> >
> >
> > CPU is running around 20% on both systems.
> >
> >
> >
> >
> >>Is there a handle in NT that an app can get at to toggle the driver
between
> >>standard and jumbo packets? Any downside to leaving jumbo enabled all
the
> >>time?
> >
> >
> > Under W2K, the knob is in the network connections applet, it is one of
> > the NIC driver options.
> >
> > So far as I know, a subnet has to be all jumbo, or all regular frames.
> >
> > /m
> >
> >
> >
--- BBBS/NT v4.01 Flag-5
* Origin: Barktopia BBS Site http://HarborWebs.com:8081 (1:379/45)SEEN-BY: 633/267 270 5030/786 @PATH: 379/45 1 106/2000 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.