On Sat, Jun 09, 2018 at 06:07:15PM -0700, Don Lewis wrote:
> On 9 Jun, Stefan Esser wrote:
>
> > 3) Programs that evenly split the load on all available cores have been
> >suffering from sub-optimal assignment of threads to cores. E.g. on a
> >CPU with 8 (virtual) cores, this resulted in
On 9 Jun, Stefan Esser wrote:
> 3) Programs that evenly split the load on all available cores have been
>suffering from sub-optimal assignment of threads to cores. E.g. on a
>CPU with 8 (virtual) cores, this resulted in 6 cores running the load
>in nominal time, 1 core taking twice
> On Fri, 8 Jun 2018 17:18:43 +0300
> Andriy Gapon wrote:
>
> > On 08/06/2018 15:27, Gary Jennejohn wrote:
> > > On Thu, 7 Jun 2018 20:14:10 +0300
> > > Andriy Gapon wrote:
> > >
> > >> On 03/05/2018 12:41, Andriy Gapon wrote:
> > >>> I think that we need preemption policies that might not
Am 07.06.18 um 19:14 schrieb Andriy Gapon:
> On 03/05/2018 12:41, Andriy Gapon wrote:
>> I think that we need preemption policies that might not be expressible as
>> one or
>> two numbers. A policy could be something like this:
>> - interrupt threads can preempt only threads from "lower"
On Fri, 8 Jun 2018 17:18:43 +0300
Andriy Gapon wrote:
> On 08/06/2018 15:27, Gary Jennejohn wrote:
> > On Thu, 7 Jun 2018 20:14:10 +0300
> > Andriy Gapon wrote:
> >
> >> On 03/05/2018 12:41, Andriy Gapon wrote:
> >>> I think that we need preemption policies that might not be expressible as
On 08/06/2018 15:27, Gary Jennejohn wrote:
> On Thu, 7 Jun 2018 20:14:10 +0300
> Andriy Gapon wrote:
>
>> On 03/05/2018 12:41, Andriy Gapon wrote:
>>> I think that we need preemption policies that might not be expressible as
>>> one or
>>> two numbers. A policy could be something like this:
On Thu, 7 Jun 2018 20:14:10 +0300
Andriy Gapon wrote:
> On 03/05/2018 12:41, Andriy Gapon wrote:
> > I think that we need preemption policies that might not be expressible as
> > one or
> > two numbers. A policy could be something like this:
> > - interrupt threads can preempt only threads
On 03/05/2018 12:41, Andriy Gapon wrote:
> I think that we need preemption policies that might not be expressible as one
> or
> two numbers. A policy could be something like this:
> - interrupt threads can preempt only threads from "lower" classes: real-time,
> kernel, timeshare, idle;
> -
Am 04.04.18 um 18:45 schrieb Andriy Gapon:
> On 04/04/2018 16:19, Stefan Esser wrote:
>> I have identified the cause of the extremely low I/O performance (2 to 6 read
>> operations scheduled per second).
>>
>> The default value of kern.sched.preempt_thresh=0 does not give any CPU to the
>> I/O
On 04/04/2018 16:19, Stefan Esser wrote:
> I have identified the cause of the extremely low I/O performance (2 to 6 read
> operations scheduled per second).
>
> The default value of kern.sched.preempt_thresh=0 does not give any CPU to the
> I/O bound process unless a (long) time slice expires
10 matches
Mail list logo
