What's holding me back from 100% utilization?

[freaksavior]

netsh int tcp set global autotuninglevel=disabled
netsh int tcp set global congestionprovider=ctcp
netsh int tcp set global ecncapability=enable
netsh int tcp set global chimney=enabled
netsh int tcp set global dca=enabled
netsh interface ipv4 show subinterface

C:\Windows\system32> netsh int tcp show global
Querying active state...

TCP Global Parameters
----------------------------------------------
Receive-Side Scaling State : enabled
Chimney Offload State : enabled
NetDMA State : enabled
Direct Cache Acess (DCA) : disabled
Receive Window Auto-Tuning Level : disabled
Add-On Congestion Control Provider : ctcp
ECN Capability : enabled
RFC 1323 Timestamps : disabled

I believe it's a physical limitation of my drive speeds, just curious if anybody else has some thoughts.

My throughput test shows I can do about 670mbps which is equal to about 67% but im getting around 75% utilization so I don't really trust it.

Currently a Airport Extreme > 30m cat5e > Netgear gig switch > PC

[AthlonX2]

Looks like drive speeds to me, unless this is an SSD

[Delta6326]

You can only go as fast as the slowest device. What devices is it going from? HDD->Router->SSD?

[FordGT90Concept]

95.3 MB/s is very good for gigabit LAN.

[freaksavior]

I actually made a crossover cable and just hooked straight up, performed the same tests with the exact same results. So assuming it's not the nic cards and they perform as they should with a throughput of 112.5Mbps then it's my drives maxing out at 95Mbps read/write.

Time to upgrade some hardware!

[Maban]

You can set up a ramdisk and do some RAM to RAM transfers.

[btarunr]

10% of the physical bandwidth goes into various overheads, rest is up to the quality of the PHY. So yeah, 95 MB/s is pretty good for 1 GbE.

[newtekie1]

I wouldn't say 95MB/s is pretty good for Gigabit. It isn't terrible, but it isn't pretty good either, I'd say OK at best. A proper setup should give 110-120MB/s with Gigabit with a constant 90-97% utilization.

This is what you should be getting.

Start of Transfer:


End of Transfer:


The two dips are where the transfer switched between files.

[freaksavior]

What are you transferring to and from though? Also, have you done tweaks?

[OneMoar]

bad switch is bad id point the finger at that netgear switch

[AthlonX2]

Originally Posted by OneMoar

bad switch is bad id point the finger at that netgear switch

I'll just assume you can't read because we already narrowed it down to the hard drives when he hooked it up direct with a crossover cable

[Aquinus]

Originally Posted by AthlonX2

I'll just assume you can't read because we already narrowed it down to the hard drives when he hooked it up direct with a crossover cable

+1: This. It sounds like your topping out your hard drive access speed. Your 1Gbit ethernet might be running at full speed but you won't notice it unless your hard drive is reading at least that fast or faster. I suspect your drive isn't reading much faster than 100MB/s tops.

[newtekie1]

Originally Posted by freaksavior

What are you transferring to and from though? Also, have you done tweaks?

Reading from the Rig2 RAID0 --> Cheap Rosewill 8-Port Switch --> Cheap Netgear 8-Port Switch --> Main Rig RAID5

I would guess your write speeds on your destination drive is probably the limiting factor for you, assuming you are using a single HDD on both ends. However, I'd run hard drive benchmarks(CrystalDiskMark) on both ends to see where the bottleneck is.

Originally Posted by Aquinus

+1: This. It sounds like your topping out your hard drive access speed. Your 1Gbit ethernet might be running at full speed but you won't notice it unless your hard drive is reading at least that fast or faster. I suspect your drive isn't reading much faster than 100MB/s tops.

Generally HDDs read faster than write, so my guess is writing to the destination drive is actually the limiting factor, but he'll have to test to find the real bottleneck.