diff options
author | David Herrmann <dh.herrmann@gmail.com> | 2015-09-29 20:56:17 +0200 |
---|---|---|
committer | David Herrmann <dh.herrmann@gmail.com> | 2015-09-29 20:56:17 +0200 |
commit | 6fe869c251790a0e3cef5b243169dda363723f49 (patch) | |
tree | e2793e54df1c835a1ce1984fffed3eda1b43bd9c /units/systemd-machined.service.in | |
parent | 8a9d23e4462aa19a17a3de463ff8e408656057af (diff) |
sd-event: don't provide priority stability
Currently, we guarantee that if two event-sources with the same priority
fire at the same time, they're always dispatched in the same order. While
this might sound nice in theory, there's is little benefit in providing
stability on that level. We have no control over the order the events are
reported, hence, we cannot guarantee that we get notified about both at
the same time.
By dropping the stability guarantee, we loose roughly 10% Heap swaps in
the prioq on a desktop cold-boot. Krzysztof Kotlenga even reported up to
20% on his tests. This sounds worth optimizing, so drop the stability
guarantee.
Diffstat (limited to 'units/systemd-machined.service.in')
0 files changed, 0 insertions, 0 deletions