mirror of
https://github.com/systemd/systemd.git
synced 2024-12-27 07:22:31 +03:00
The systemd System and Service Manager
b439282e0b
journal_file_move_to_object() can skip the second journal_file_move_to() call if the first one already mapped a sufficiently large area. Now that mmap_cache_get() returns the size of the mapped area when asked, ask for the size and only perform the second call if the required size exceeds the mapped size instead of the object header size. This results in a nice performance boost in my testing, even with a corpus of many small logs burning much CPU time elsewhere: Before: # time ./journalctl -b -1 --no-pager > /dev/null real 0m16.330s user 0m16.281s sys 0m0.046s # time ./journalctl -b -1 --no-pager > /dev/null real 0m16.409s user 0m16.358s sys 0m0.048s # time ./journalctl -b -1 --no-pager > /dev/null real 0m16.625s user 0m16.558s sys 0m0.061s After: # time ./journalctl -b -1 --no-pager > /dev/null real 0m15.311s user 0m15.257s sys 0m0.046s # time ./journalctl -b -1 --no-pager > /dev/null real 0m15.201s user 0m15.135s sys 0m0.062s # time ./journalctl -b -1 --no-pager > /dev/null real 0m15.170s user 0m15.113s sys 0m0.053s |
||
---|---|---|
.github | ||
.mkosi | ||
catalog | ||
coccinelle | ||
docs | ||
factory/etc | ||
hwdb | ||
m4 | ||
man | ||
network | ||
po | ||
rules | ||
shell-completion | ||
src | ||
sysctl.d | ||
system-preset | ||
sysusers.d | ||
test | ||
tmpfiles.d | ||
tools | ||
units | ||
xorg | ||
.dir-locals.el | ||
.editorconfig | ||
.gitattributes | ||
.gitignore | ||
.mailmap | ||
.travis.yml | ||
.vimrc | ||
.ycm_extra_conf.py | ||
autogen.sh | ||
CODING_STYLE | ||
configure.ac | ||
DISTRO_PORTING | ||
ENVIRONMENT.md | ||
HACKING | ||
LICENSE.GPL2 | ||
LICENSE.LGPL2.1 | ||
Makefile-man.am | ||
Makefile.am | ||
meson_options.txt | ||
meson.build | ||
mkosi.build | ||
mkosi.default | ||
NEWS | ||
README | ||
README.md | ||
TODO |
systemd - System and Service Manager
Details
General information about systemd can be found in the systemd Wiki.
Information about build requirements are provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the HACKING file for information how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list or join our IRC channel.