Virtual Routers makes the filetransfer slow. Is it my hardware or my configuration? Plus routing question.


lab server specs:
cpu: intel g3220 3 ghzmemory: 20 gb ram
hdd: 2x 250 gb ssd , 1x 500gb ssd (for vm's)

running above server lab server , works fine labs speed not  issue. running hyper-v 2012r2 latest patches. have 1 lab-network , 1 production-network. using internal vswitch, , using virtual gw/router/fw (or correct term is) protect network , external switch (see diagram below). using pfsense , windows server 2012r2 rras , vpn service activated. problem getting very, slow speed if transfer data between lab-network , production-network. using nifty program called netio benchmark, , speed between dc01 in lab-networkto svr1 in production-networkis 192 mbit (24 mb/sek). if connect computer gs108v3 switch , run netio dc01 in lab-network i staggering 424 mbit (53 mb/sek). my conclusion is virtual routers the bottlenecks in lab-setup. if transfer files within network ~800 mbit, aswell between hypervisors 850 mbit or better. cant see cpu, or memory peaks in resource monitor.

if traceroute dc01 on lab-network svr1 on production-network following result, should not ignore 192.168.1.1 , go directly to srv2012rtr, save hop?

1    <1 ms    <1 ms    <1 ms  172.16.16.1
2    <1 ms     1 ms    <1 ms  192.168.1.1
3     1 ms     *        1 ms  srv2012rtr [192.168.1.1]
4     1 ms     1 ms     1 ms  svr1 [10.10.0.230]

i have been playing memory, virtual cores , makes no different in speed. 

just want confirm hardware , not configuration makes slow. :-)


also, time add hop going impact network performance.

and, can network configuration itself, not router vm, depending on routing tables.

start disabling vmq.

you can consider giving router vm sr-iov vnic channel gets out of vm nic.


brian ehlert
http://itproctology.blogspot.com
learn. apply. repeat.



Windows Server  >  Hyper-V



Comments

Popular posts from this blog

Motherboard replacement

Cannot create Full Text Search catalog after upgrading to V12 - Database is not fully started up or it is not in an ONLINE state

Remote Desktop App - Error 0x207 or 0x607