networking - Software Routing -


"commercial software routers companies such vyatta can typically attain transfer data @ speeds of 3 gigabits per second. isn’t fast enough take advantage of full speed of typical network card, operates @ 10 gigabits per second." [1]

how speed of network interface card relevant in scenario? aren't software routers connecting multiple virtual machines running on same physical host? [2] unless pc has multiple network interface cards, unlikely functions packet switch between different physical hosts.

my interpretation suggests there seem exist 2 different kinds of software routing: (1) embedding real time operating system on actual router. (2) writing application layer code on pc can handle packets being transmitted between different virtual machines running on that very pc. correct?

it depends on router doing. if it's literally looking @ static route table , forwarding packets out interface, there isn't hit in performance.

it's when things nat, crypto, qos, spi... see performance degradation. hardware vendors using custom silicon process more advanced features, allows higher throughput packet forwarding.

now merchant silicon fast enough , open source applications getting better, performance gap closing.

it depends on use case far want use. i've gone both , not seen performance hits, software versions weren't handling high throughput workloads.


Comments

Popular posts from this blog

java - Suppress Jboss version details from HTTP error response -

gridview - Yii2 DataPorivider $totalSum for a column -

Sass watch command compiles .scss files before full sftp upload -