Thanks Michael. I did try out these options and that works as per the documentation. but, the problem comes when I want to run multiple instances without overlapping CPU's. For example, lets say I have a system with 2 NUMA's with each having 24 cores (12 physical + 12 HT) and second numa has same replica. So, in this powerful system I want to run 8 instances with 6 cores (3 physical + 2 HT) each (without overlapping! between cores). If I use pools option and start multiple instances (with each --pools x,- ) then they doesn't seems to utilizing all the cores and also seeing overlaps.
Is there a reason why the CPU pinning was done internally? Thanks, *Raj* *Do it today or leave it !!!* On Wed, Apr 10, 2019 at 2:16 AM Michael Lackner < [email protected]> wrote: > I believe you should be able to do that via the --pools <string> or > --numa-pools <string> > command line option, in case you're using the cli version of x265. > > Documentation of the syntax can be found here: > > https://x265.readthedocs.io/en/default/cli.html#cmdoption-pools > > That won't allow you to use numactl on the process, but given the > parameters' flexibility > you should be able to pin the processes' threads on specific NUMA nodes as > well as > individual cores. > > Let's say you have a single NUMA node, then I guess "--pools 8" would > limit the process to > the first 8 logical cores of the machine. > > For a 2-node NUMA system, I assume you could do: "--pools 8,-", which > should use a maximum > of 8 logical cores on node 0 and zero cores on node 1. > > Not sure how to do it on a flat topology (without any NUMA) though. But I > guess most > modern systems are NUMA-aware anyway. > > On 4/10/19 9:35 AM, Raj K Chinna wrote: > > Hi, > > > > I am been having trouble with x265 benchmark app CPU allocation limits. > > Even though I allocate 8 cores (16 available) from my cloud instance the > > app still goes and schedules threads on all 16 cores. Upon checking looks > > like x265 has inbuilt CPU binding mechanism and that doesn't get limited > by > > numactl. > > > > Is there a way I can disable inbuilt CPU resource management and control > > CPU allocation using numactl. > > > > Thanks, > > *Raj* > > *Do it today or leave it !!!* > > > > > > _______________________________________________ > > x265-devel mailing list > > [email protected] > > https://mailman.videolan.org/listinfo/x265-devel > -- > Michael Lackner > Lehrstuhl für Informationstechnologie (CiT) > Montanuniversität Leoben > Tel.: +43 3842 402 1505 | Mail: [email protected] > Fax.: +43 3842 402 1502 | Web: http://institute.unileoben.ac.at/infotech > _______________________________________________ > x265-devel mailing list > [email protected] > https://mailman.videolan.org/listinfo/x265-devel >
_______________________________________________ x265-devel mailing list [email protected] https://mailman.videolan.org/listinfo/x265-devel
