On 3/23/19 11:56 AM, Eric W. Biederman wrote:
> Jeff Mahoney writes:
>
>> On 4/24/18 10:14 AM, Eric W. Biederman wrote:
>>> je...@suse.com writes:
>>>
From: Jeff Mahoney
Hi all -
I recently encountered a customer issue where, on a machine with many TiB
of memory
Jeff Mahoney writes:
> On 4/24/18 10:14 AM, Eric W. Biederman wrote:
>> je...@suse.com writes:
>>
>>> From: Jeff Mahoney
>>>
>>> Hi all -
>>>
>>> I recently encountered a customer issue where, on a machine with many TiB
>>> of memory and a few hundred cores, after a task with a few thousand
On 4/24/18 10:14 AM, Eric W. Biederman wrote:
> je...@suse.com writes:
>
>> From: Jeff Mahoney
>>
>> Hi all -
>>
>> I recently encountered a customer issue where, on a machine with many TiB
>> of memory and a few hundred cores, after a task with a few thousand threads
>> and hundreds of files
On 4/24/18 10:14 AM, Eric W. Biederman wrote:
> je...@suse.com writes:
>
>> From: Jeff Mahoney
>>
>> Hi all -
>>
>> I recently encountered a customer issue where, on a machine with many TiB
>> of memory and a few hundred cores, after a task with a few thousand threads
>> and
On 4/24/18 10:14 AM, Eric W. Biederman wrote:
> je...@suse.com writes:
>
>> From: Jeff Mahoney
>>
>> Hi all -
>>
>> I recently encountered a customer issue where, on a machine with many TiB
>> of memory and a few hundred cores, after a task with a few thousand threads
>> and hundreds of files
On 4/24/18 2:17 AM, Alexey Dobriyan wrote:
> On Mon, Apr 23, 2018 at 10:21:01PM -0400, je...@suse.com wrote:
>> Memory pressure isn't really an issue on this machine, so we
>> end up using well over 100GB for proc files.
>
> Text files at scale!
>
>> With these patches applied, running the same
On 4/24/18 2:17 AM, Alexey Dobriyan wrote:
> On Mon, Apr 23, 2018 at 10:21:01PM -0400, je...@suse.com wrote:
>> Memory pressure isn't really an issue on this machine, so we
>> end up using well over 100GB for proc files.
>
> Text files at scale!
>
>> With these patches applied, running the same
je...@suse.com writes:
> From: Jeff Mahoney
>
> Hi all -
>
> I recently encountered a customer issue where, on a machine with many TiB
> of memory and a few hundred cores, after a task with a few thousand threads
> and hundreds of files open exited, the system would softlockup.
je...@suse.com writes:
> From: Jeff Mahoney
>
> Hi all -
>
> I recently encountered a customer issue where, on a machine with many TiB
> of memory and a few hundred cores, after a task with a few thousand threads
> and hundreds of files open exited, the system would softlockup. That
> issue was
On Mon, Apr 23, 2018 at 10:21:01PM -0400, je...@suse.com wrote:
> Memory pressure isn't really an issue on this machine, so we
> end up using well over 100GB for proc files.
Text files at scale!
> With these patches applied, running the same testcase, the proc_inode
> cache only gets to about
On Mon, Apr 23, 2018 at 10:21:01PM -0400, je...@suse.com wrote:
> Memory pressure isn't really an issue on this machine, so we
> end up using well over 100GB for proc files.
Text files at scale!
> With these patches applied, running the same testcase, the proc_inode
> cache only gets to about
From: Jeff Mahoney
Hi all -
I recently encountered a customer issue where, on a machine with many TiB
of memory and a few hundred cores, after a task with a few thousand threads
and hundreds of files open exited, the system would softlockup. That
issue was (is still) being
From: Jeff Mahoney
Hi all -
I recently encountered a customer issue where, on a machine with many TiB
of memory and a few hundred cores, after a task with a few thousand threads
and hundreds of files open exited, the system would softlockup. That
issue was (is still) being addressed by Nik
13 matches
Mail list logo