update my fork2 #3
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* add strict checks to waiting queue * waiting queue implementation purely using atomics * trylock should insist if we are the potential winner
fixed mixed up ordering
revert coverity fix; count also the number of entries to release shutdown
* load rrdcontext dimensions in batches * Batch load all dimensions of a host --------- Co-authored-by: Stelios Fragkakis <[email protected]>
fix aral memory accountig
Co-authored-by: ilyam8 <[email protected]>
* benchmark locks; new rw-spinlock implementation; performance improvements on waitq * benchmark and stress r/w locks
…/src/go (#19322) Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
fix fds leak in health
Co-authored-by: ilyam8 <[email protected]>
* inline functions related to metrics ingestion * move pulse outside the lock * cleanup senders in connector thread - untested * receiver and sender cleanup * buffer functions inlining * more inlining * do not disconnect receivers when the sender fails * heavy parts of sender connect/disconnect run with connector unlocked
Better fix coverity issue, always cleanup
* fixed bug where contexts stay not-live, although they are collected * small optimization
allow dbengine to read at offsets above 4GiB
Co-authored-by: Ilya Mashchenko <[email protected]>
Co-authored-by: ilyam8 <[email protected]>
* Add LTO support in CMake build system. Internally, CMake calls LTO ‘Interprocedural Optimization’, and it provides functionality for checking for support for this as well as enabling it by default for targets. This leverages that support to auto-detect LTO and enable it if it’s supported. * Default to disabling LTO for Debug builds. * Add handling for LTO to netdata installer code. * Switch back to DISABLE_LTO as option name. Using `ENABLE_LTO` leads to a possibility for confusion among users, as it does behave in the most intuitive manner. Instead of ensuring that LTO is used (and thus behaving like every other `ENABLE_*` option we have), it allows the usage LTO if it’s supported. Thus a build with `-DENABLE_LTO=True` may not actually be built with LTO. By instead using `DISABLE_LTO`, the behavior matches up directly with how most people are likely to interpret the meaning, because a build with `-DDISABLE_LTO=True` will _never_ have LTO flags added to the compiler/linker flags. * Fix condition for determining default for DISABLE_LTO. * Turn off LTO auto-detection in RPM package builds. On pretty much all RPM platforms, the RPM build process itself will correctly add the required compiler flags when building, so we don’t actually need to auto-detect LTO support in CMake here. Additionally, on at least some RPM platforms, CMake’s auto-detection for LTO support actually breaks the build when used. * Disable function and data sections when using LTO. On at least some systems, `-fdata-sections` combined with LTO reliably causes failures at link time with our code. The final binary size on systems where the combination _works_ differs by no more than a few KiB on average (tested on 64-bit x86 on Ubuntu 22.04, Debian 12, Fedora 39, and Rocky Linux 9), so we’re not actually getting almost any benefit out of using both with things as they are now, but LTO gives us a meaasurable performance improvement that per-function and per-data sections do not. * Restructure in-line with current repo state. * Disable LTO on Windows builds since it doesn’t work there. * Fix compiler flag handling order. * Switch LTO option name to USE_LTO for consistency with USE_MOLD.
Co-authored-by: ilyam8 <[email protected]>
Co-authored-by: ilyam8 <[email protected]>
* format_ebpf: Format ebpf.[ch] * format_ebpf: Format ebpf_apps.[ch] * format_ebpf: Format ebpf_cachestat.[ch] * format_ebpf: Format ebpf_cgroup.[ch] * format_ebpf: Format ebpf_dcstat.[ch] * format_ebpf: Format ebpf_disk.[ch] * format_ebpf: Format ebpf_fd.[ch] * format_ebpf: Format ebpf_filesystem.[ch] * format_ebpf: Format ebpf_functions.[ch] * format_ebpf: Format ebpf_hardirq.[ch] * format_ebpf: Format ebpf_mdflush.[c] * format_ebpf: Format ebpf_mount.[ch] * format_ebpf: Format ebpf_oomkill.[c] * format_ebpf: Format ebpf_process.[ch] * format_ebpf: Format ebpf_shm.[ch] * format_ebpf: Format ebpf_socket.[ch] * format_ebpf: Format ebpf_softirq.[c] * format_ebpf: Format ebpf_swap.[ch] * format_ebpf: Format ebpf_sync.[ch] * format_ebpf: Format ebpf_unittest.[ch] * format_ebpf: Format ebpf_vfs.[ch]
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Component Name
Additional Information