Is there latency overhead while using static IP routing?

i have windows 2008 r2 server 4 nics. 2 x 1 gbe , 2 x 10 gbe. want traffic go through 10 gbe nic 1 particular application specific ip addresses.

the obvious solution write static routes.

however application very low latency hence expensive server , 10 gbe solarflare nic.

the application .net code connects specific remote ports using sockets once in life time..

is correct assume actual 'routing' happens @ moment when local socket connects remote socket , ip taffic going later without windows software routing involved... am right assume there 0 impact on latency using windows routing?

hi,

according description, understand app cannot afford high latency, , solution found add static route. , know if static route cause overhead lantency, right?

based on knowledge, adding static route add 1 entry route table. when traffic go through nic card, match entry in route table. if traffic mathes static route, go ahead destination records, or find other 1 go.

so, won't cause overhead latency. , think even makes more effective.

besides, windows static routing not kick in on socket connect , does impact on each , every tcp packet sent , received.

if have concern it, please feel free let me know.

thanks,

best regards,

annie

Windows Server  >  Network Infrastructure Servers