ESXi - N40L - Slow Network Speeds


Recommended Posts

Hi Guys,

I am running 2 VMS, WHS2011 and WinXP, both have vmxnet3 drivers installed. The XP network says its running at 1.4GB/s and the WHS network is running at 10GB/s.

When I transfer files from one VM to the other i am getting speeds of 2MB/s. Why is this so slow??

I have run iperf and get speeds of 102 Mbits/sec

whilst the file transfer is in progress CPU usage is around 10% on both VM machines, but when I run iperf, CPU usage maxs out at 100% on the XP VM and about 55-65% on the WHS2011 VM.

Is the CPU being at 100% throttling the network?

I am running one physical network card,

Can anyone shed some light on this? I am a newbie to VMs but not to computers :)

thanks!

Link to comment
https://www.neowin.net/forum/topic/1128838-esxi-n40l-slow-network-speeds/
Share on other sites

Those speeds (That are reported in Windows) are for the Virtual Adapters. Although its true that transferring speeds between VM's on the same does write directly between Memory and not hit the wire so to speak. The speed will only be 1Gbps on the Physical Adapter by the way. Have you applied all the latest patches to ESXi, I would highly recommend it. My CPU usage is always really low, Infact I am surprised at how efficient it is. I just need some more memory in my baby!

http://www.vmware.com/patchmgr/findPatch.portal

SK[' timestamp=1357165637' post='595429082]

If your using the vmxnet3 driver shouldn't it be showing 10GB?

*Edit*

Just checked my XP VM out and indeed it shows 1.4GB. Never noticed that before.

102Mbit is about right for a 1GB NIC no?

It might be for XP that it shows 1.4Gbps, Don't have one to test it. I have only seen it at 10GBps. Budman could chime in though and tell us if this is the case.

Yes your right just over 100MB for 1Gbps.

So I don't have an XP vm currently - but I could fire one up for sure.

But between my nas vm and win7 vm I show this, btw 102mbps is SLOW if you showing connected at gig speeds.

C:\Windows\System32>iperf -c storage -w 256k
------------------------------------------------------------
Client connecting to storage, TCP port 5001
TCP window size:  256 KByte
------------------------------------------------------------
[276] local 192.168.1.210 port 49233 connected with 192.168.1.8 port 5001
[ ID] Interval	   Transfer	 Bandwidth
[276]  0.0-10.0 sec   599 MBytes   502 Mbits/sec

I should see if I can get that up a bit - my physical machines see much higher. 800Mbps should be seen on a gig network fairly easy.

So file copy from my nas vm to my win7 vm

post-14624-0-27431800-1357221554.png

So I am seeing 50MBytes per second in this test.

But curious to what disks your writing/reading from - are you just trying to copy a file from datastore drive of vm to another datastore drive on the other vm. My nas has raw access to the 3 drives it uses for storage. So the above tests were from one of those disks to the datastore drive of the win7 vm

Also curious --- you gave 4GB to each of your VMs, do you have more than 8 in your N40L?

So I did a test that I think more reflects what your doing more likely. And that is from datastore drive to datastore drive of each VM. And in that test I got only 23MBps

post-14624-0-56310600-1357222192.png

What else is your datastore disk doing at the time?? That performance is not going to be the best, your 2 different VMs are accessing the same physical disk. So yeah there is going to be some contention for time.

thanks, i have 10GB of memory in my N40L, an 8Gb and a 2Gb stick.

I have a drivepool in WHS, consisting of 2TB and 1.5TB WD Green drives

I am transferring files from the pool to the XP machine which has a second 2TB drive attached.

The VMs themselves were stored on the 250Gb drive, but I have moved them to another 2TB drive for now.

The ESXi is installed on a 8GB USB pen drive.

Thanks

a bit of progress maybe?

under the WHS2011 VM

If i "pull" a file from the xp machine to the WHS drivepool i get speeds of 13.5MB/s

if i "push" a file from the WHS drivepool to the xp machine i get speeds of 2MB/s

could that be a write issue with the XP HDD ? (E: 2TB)

thats still pretty crappy for a gig network. If I do a iperf or file copy to a physical machine from the vm I get this

C:\test>robocopy \\storage\media\cleanup c:\test test.mp4

-------------------------------------------------------------------------------
   ROBOCOPY	 ::	 Robust File Copy for Windows
-------------------------------------------------------------------------------

  Started : Thu Jan 03 10:31:22 2013

   Source = \\storage\media\cleanup\
	 Dest : c:\test\

	Files : test.mp4

  Options : /COPY:DAT /R:1000000 /W:30

------------------------------------------------------------------------------

						   1	\\storage\media\cleanup\
100%		New File			 650.8 m		test.mp4

------------------------------------------------------------------------------

			   Total	Copied   Skipped  Mismatch	FAILED	Extras
	Dirs :		 1		 0		 1		 0		 0		 0
   Files :		 1		 1		 0		 0		 0		 0
   Bytes :  650.86 m  650.86 m		 0		 0		 0		 0
   Times :   0:00:09   0:00:09					   0:00:00   0:00:00


   Speed :			74150984 Bytes/sec.
   Speed :			4242.953 MegaBytes/min.

   Ended : Thu Jan 03 10:31:31 2013

C:\test>iperf -c storage -w 256k
------------------------------------------------------------
Client connecting to storage, TCP port 5001
TCP window size:  256 KByte
------------------------------------------------------------
[336] local 192.168.1.100 port 16077 connected with 192.168.1.8 port 5001
[ ID] Interval	   Transfer	 Bandwidth
[336]  0.0-10.0 sec  1012 MBytes   849 Mbits/sec

Notice the 800+ Mbits per second over gig.. And in the 70MBps for file pull from my VM.

Do an iperf test from your physical to your VM, using a higher window size, say -w 256k You can see example of this test in my above output. On the server set it up with iperf -s -w 256k

Do you have 2 physical boxes we can play with - 295Mbps is that your iperf test.. That is pretty crappy for a gig network. Did you use the larger window size for your test?

at 8.59 mbps -- is that over wireless or something? Are you reading writing from a USB disk or something.. That is just horrific performance.

Damn you beat me too it! I was going to say that. How are they formatted?

I added the drives under the vclient and formatted them via windows - is that right? am a novice with ESXi

Do you have 2 physical boxes we can play with - 295Mbps is that your iperf test.. That is pretty crappy for a gig network. Did you use the larger window size for your test?

at 8.59 mbps -- is that over wireless or something? Are you reading writing from a USB disk or something.. That is just horrific performance.

yes, those figures are are with iperf on a wired Gb network

I've just performed another iperf test

physcial XP machine set as server (1Gb network) - wired

physical win7 laptop set as client (100Mb network) - wired

and i get 87Mbits/sec

the laptop has only got a 100Mb network card, so thats the max on this network - this is for this test only.

Well 87mbps on 100mbit connection is about right.. Best you could see on 100mbit is around mid 90's -- think best I have ever seen is 97 something. Never ever going to see actual speed of the connection.

But on gig you should be seeing closer to 800s vs your under 300 number.

So question for you on your VM whs - did you give whs raw access to the disks, or did you create vmfs on the disks that the OS has access to.

So for example on my storage box

post-14624-0-36278900-1357239638.jpg

Notice that the 3 disks I have given it to use in a drive pool the disks are raw mapped, and then above that you see the virtual disk (on the datastore drive) that is the vmfs for the OS installed too.

Here is a guide on how to do that

http://vm-help.com/esx40i/SATA_RDMs.php

So for example here is my maps

/vmfs/volumes/4f677e4a-81443006-5233-2c768aadf656/RDMs # ls -la

drwxr-xr-x 1 root root 1120 Dec 26 13:12 .

drwxr-xr-t 1 root root 5180 Dec 29 14:59 ..

-rw------- 1 root root 2000398934016 Apr 7 2012 rdm1-rdmp.vmdk

-rw------- 1 root root 521 Dec 26 13:12 rdm1.vmdk

-rw------- 1 root root 750156374016 Apr 16 2012 rdm2-rdmp.vmdk

-rw------- 1 root root 520 Dec 26 13:12 rdm2.vmdk

-rw------- 1 root root 750156374016 Apr 14 2012 rdm3-rdmp.vmdk

-rw------- 1 root root 520 Dec 26 13:12 rdm3.vmdk

/vmfs/volumes/4f677e4a-81443006-5233-2c768aadf656/RDMs #

So couple of things to deal with on your slow performance - why your iperf between vms is so slow. And then make sure that your drive access is as fast as it can be. How are attaching the disks to your VMs could be a limiting factor - and have to look into the speed between vms from a network as well. I do recall seeing above 1Gbps before on iperf between machines

yeah just looked up a old thread about N40L performance - and in a test there I was seeing 1.5Gbps between vms - have to take a look why only seeing 500mbps now

https://www.neowin.net/forum/topic/1071115-esxi-hp-microserver-n40l-performance/page__view__findpost__p__594826393

post-14624-0-44916300-1335455395.jpg

So I got something not quite right as well - wonder what would of changed?? I know the client is different in this test. Have to look to getting my between vms speeds back to that over 1Gbps ;)

This is a copy from A Win7 VM to my physical Desktop over a 1GB switch. The discs are thin provisioned.


-------------------------------------------------------------------------------
ROBOCOPY :: Robust File Copy for Windows
-------------------------------------------------------------------------------
Started : 04 January 2013 09:16:13
Source : VM7COMPUTER
Dest : C:\Users\Andrew\Desktop\
Files : SOME.FILE
Options : /DCOPY:DA /COPY:DAT /R:1000000 /W:30
------------------------------------------------------------------------------
1 VM7COMPUTER

100% New File 701.8 m SOME.FILE
------------------------------------------------------------------------------
Total Copied Skipped Mismatch FAILED Extras
Dirs : 1 0 0 0 0 0
Files : 1 1 0 0 0 0
Bytes : 701.88 m 701.88 m 0 0 0 0
Times : 0:00:06 0:00:06 0:00:00 0:00:00

Speed : 108010209 Bytes/sec.
Speed : 6180.393 MegaBytes/min.
Ended : 04 January 2013 09:16:20
[/CODE]

This is copying from a Win XP machine to my physical desktop over the same switch with the VM in the same datastore. Basically, there is nothing different from the above other than its a VM with XP rather than 7.

[CODE]
-------------------------------------------------------------------------------
ROBOCOPY :: Robust File Copy for Windows
-------------------------------------------------------------------------------
Started : 04 January 2013 10:10:43
Source : VMXPCOMPUTER
Dest : C:\Users\Andrew\Desktop\
Files : SOME.FILE
Options : /DCOPY:DA /COPY:DAT /R:1000000 /W:30
------------------------------------------------------------------------------
1 VMXPCOMPUTER
100% New File 851.2 m SOME.FILE
------------------------------------------------------------------------------
Total Copied Skipped Mismatch FAILED Extras
Dirs : 1 0 0 0 0 0
Files : 1 1 0 0 0 0
Bytes : 851.20 m 851.20 m 0 0 0 0
Times : 0:00:13 0:00:13 0:00:00 0:00:00

Speed : 65230532 Bytes/sec.
Speed : 3732.521 MegaBytes/min.
Ended : 04 January 2013 10:10:57
[/CODE]

XP seems to be much slower than its predecessor. I know they are slightly different file sizes but the speed speaks for itself.

TBH as I run with such a small amount of resources I would sooner use XP over 7 yet XP feels much slower than 7 does as a VM on my MicroServer. Windows 2008 R2 feels much snappier than XP does. I need to ditch my XP machine really as these tests above prove 7 is not performing how it should.

The host is a HP MicroServer (N36L so the mk1 version).

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      590
    2. 2
      +Edouard
      186
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      67
  • Tell a friend

    Love Neowin? Tell a friend!