|
From: | Rob Sargent |
Subject: | Re: Cannot specify the number of threads for parsort |
Date: | Fri, 17 Feb 2023 13:49:19 -0700 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1 |
Are you in the high memory consumption scenario which Nigel describes?It looks like we may not get what we kindly asked for. So, I started making "mcesort" using Perl MCE's chunking engine.
On Thu, Feb 16, 2023 at 5:08 AM Nigel Stewart <nigels@nigels.com> wrote:
Can you elaborate on what I am missing from the picture?
Ole,
Perhaps your workloads are more CPU and I/O intensive, and latency is less of a priority.
If the workload is memory-intensive, that can be the more important constraint than
the number of available cores. If the workload is interactive (latency-sensitive) it's
undesirable to have too many jobs in flight competing for CPU and I/O, delaying each other.
- Nigel
[Prev in Thread] | Current Thread | [Next in Thread] |