Hi Nikos. Yes, you are right, but sometimes java application show better performance under high load when used 1.2-1.5 process per core. Thicker loading is not always bad.
2016-04-11 18:23 GMT+03:00 Nikos R. Katsipoulakis <[email protected]>: > Hello both, > > Andrey, I believe its better to use one executor thread per core and only > one worker process per socket. This way, the executor threads communicate > with each other using LMAX Disruptor queues (therefore less latency) and > Netty is used only when a message needs to be sent to another executor > thread on a different machine. > > Also, if you need a lot of memory, you can start your worker process with > as much Heap memory you want. > > Cheers, > Nikos > > On Mon, Apr 11, 2016 at 9:15 AM, Andrey Dudin <[email protected]> wrote: > >> Hi, >> It's depend by code. Usually starting from 1-1,5 process per core. >> >> 2016-04-11 16:10 GMT+03:00 Sai Dilip Reddy Kiralam < >> [email protected]>: >> >>> >>> Hi All, >>> >>> I'm using a 16 core cpu as my supervisor node.My doubt is How many >>> supervisor.slots should I set in supervisor storm.yaml conf file ?Is there >>> any formula to set no of slots based on the cpu core. >>> >>> Thanks in Advance >>> >>> >>> *Best regards,* >>> >>> *K.Sai Dilip Reddy.* >>> >> >> >> >> -- >> С уважением Дудин Андрей >> > > > > -- > Nikos R. Katsipoulakis, > Department of Computer Science > University of Pittsburgh > -- С уважением Дудин Андрей
