That is an interesting use case although we need to make clear that running multiple instances on the same server will likely not provide linear performance increase. Can you provide more information about your concurrency target? I.e. how many instances are you planning to run and on what hardware resources (RAM, cores, NIC)?
Regarding resource partitioning easiest would be to take advantage of containerization (cgroups) with the goal of being able to run multiple instances of the nfvbench container (each running the nfvbench orchestration and 1 instance of trex). This should take care of the nfvbench to trex communication which stays internal to each container instance (the 127.0.0.1 subnet is specific to each container instance - so no need to have different zmq ports as they will run on distinct subnets - to be confirmed) The externally visible resources across container instances would still need to be solved through container parameters: * Nfvbench REST service port - already supported (if used) * Trex NIC and ports selection – already supported in nfvbench config * Huge pages configuration in Trex might require some tweaking and impact the server overall huge page configuration * Platform latency and master thread id, socket and threads - we will need to check with the trex team how to work out core partitioning across containers Thanks Alec From: <opnfv-tech-discuss@lists.opnfv.org> on behalf of François-Régis MENGUY <francoisregis.men...@orange.com> Date: Friday, January 11, 2019 at 5:27 AM To: "opnfv-tech-discuss@lists.opnfv.org" <opnfv-tech-discuss@lists.opnfv.org> Hello, NFVBench needs to define TRex parameters in order to tune resources used by this process and permit multiple instance of NFVBench on the same compute node.
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#22643): https://lists.opnfv.org/g/opnfv-tech-discuss/message/22643 Mute This Topic: https://lists.opnfv.org/mt/29007935/21656 Mute #nfvbench: https://lists.opnfv.org/mk?hashtag=nfvbench&subid=2783016 Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
