Bug #524
closedDecide an appropriate subbuffer size for per-uid UST buffers
100%
Description
Currently, per-uid buffers use the same default subbuffer size as per-pid buffers, but it does not make sense to use this value, since the reason for having small per-pid buffers (that we have typically many pids in a system) does not apply to per-uid buffers.
DG Updated by David Goulet over 12 years ago
- Status changed from New to Confirmed
Any suggestions ?
It depends on so much "unknown" variables such as the throughput, number of apps, number of events, ...
We can go 4 or 8 times bigger? Tbh, either a wild guest or we do a survey to our users. :)
MD Updated by Mathieu Desnoyers over 12 years ago
I'm tempted to derive the size based on the values we use for kernel tracing, and divide that value e.g. by 2, assuming we can have typically up to 2 users tracing in a system.
Thoughts ?
Thanks,
Mathieu
Updated by Anonymous over 12 years ago
Mathieu Desnoyers wrote:
I'm tempted to derive the size based on the values we use for kernel tracing, and divide that value e.g. by 2, assuming we can have typically up to 2 users tracing in a system.
This would make sense for defining the default value. However, would it be a separate entry in defaults.h?
MD Updated by Mathieu Desnoyers over 12 years ago
Yes, we'd split the current UST default entries into UST_PID and
UST_UID.
Thanks,
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
DG Updated by David Goulet over 12 years ago
Yah most probably it will be a default value specific to per UID buffers.
So the Kernel size is: 262144 bytes so dividing this by two makes: 131072 bytes --> 128K
Seems good as any other values to me :)
DG Updated by David Goulet over 12 years ago
- Status changed from Confirmed to Resolved
- % Done changed from 0 to 100
Applied in changeset 0a9c649428b2ea8d4e743aebc12585eeb58fcf64.