If you were within a container, localhost should have worked depending on configuration. The emulator configuration parameter (platform XML) 'controlportendpoint' specifies the listen endpoint for the control port:
<param name="controlportendpoint" value="0.0.0.0:47000"/> We use the lxc.cgroup.cpuset.cpus option in our lxc config files to assign specific cpus. For example: lxc.cgroup.cpuset.cpus=17 You can also use 'taskset' to assign processes to a specific cpu. -steve On 08/20/2015 09:53 AM, Dan O'Keeffe wrote: > Hey Stephen, > > On 20/08/15 13:52, Steven Galgano wrote: >> Dan, >> >> If your emulated nodes are each running an emulator instance (emane >> application) inside their individual network namespaces, you will need >> to use their hostnames. >> >> For example: >> >> # emanesh node-1 get table '*' mac > > Great, thanks. I had tried emanesh localhost from within the container > but it didn't work, didn't occur to me to try the actual hostname. > >> >> Improving timer latency is more a function of adding CPU resources to >> the emulation. For example, adding additional servers, reducing server >> load or assigning a specific core or cores to each container. >> > > Is there a quick way to assign specific cores to a container to test > whether your last suggestion helps? > > As far as I can tell, I should have sufficient resources on the machine > I'm using. It has 32 cores, and I'm trying to run a CORE-EMANE emulation > with 25 nodes. From looking at htop the cpu usage of each core is only > around 30%, with the cpu utilization of the emane processes ranging from > 10-50%. Some of the services running on the nodes occasionally use a lot > of CPU, but given the low overall utilization I would think this > shouldn't be a problem? > > Thanks for your help, > Dan > > _______________________________________________ emane-users mailing list [email protected] http://pf.itd.nrl.navy.mil/mailman/listinfo/emane-users
