On Thu, Jan 31, 2019 at 11:12 PM Xavi Hernandez
wrote:
> On Fri, Feb 1, 2019 at 7:54 AM Vijay Bellur wrote:
>
>>
>>
>> On Thu, Jan 31, 2019 at 10:01 AM Xavi Hernandez
>> wrote:
>>
>>> Hi,
>>>
>>> I've been doing some tests with the global thread pool [1], and I've
>>> observed one important
On Fri, Feb 1, 2019 at 7:54 AM Vijay Bellur wrote:
>
>
> On Thu, Jan 31, 2019 at 10:01 AM Xavi Hernandez
> wrote:
>
>> Hi,
>>
>> I've been doing some tests with the global thread pool [1], and I've
>> observed one important thing:
>>
>> Since this new thread pool has very low contention
On Thu, Jan 31, 2019 at 10:01 AM Xavi Hernandez
wrote:
> Hi,
>
> I've been doing some tests with the global thread pool [1], and I've
> observed one important thing:
>
> Since this new thread pool has very low contention (apparently), it
> exposes other problems when the number of threads grows.
Hi,
I've been doing some tests with the global thread pool [1], and I've
observed one important thing:
Since this new thread pool has very low contention (apparently), it exposes
other problems when the number of threads grows. What I've seen is that
some workloads use all available threads on
On Sun, Jan 27, 2019 at 8:03 AM Xavi Hernandez
wrote:
> On Fri, 25 Jan 2019, 08:53 Vijay Bellur
>> Thank you for the detailed update, Xavi! This looks very interesting.
>>
>> On Thu, Jan 24, 2019 at 7:50 AM Xavi Hernandez
>> wrote:
>>
>>> Hi all,
>>>
>>> I've just updated a patch [1] that
