Starting work on memory optimization in lxqt components #507
Conversation
This file contains hidden or 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
- Category 64 bytes (1 cpu cacheline) - Cat_percent 80 bytes (2 cpu cacheline)
- in CMake added checks. If AVX2 supported then add compile flags.
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.
@tsujan, my major branch is aimed at reducing RAM consumption, or rather reducing size structures, aligning them in memory, and using SIMD instructions.
Added new variant implementatio SIMD for x_atoi().
On release build has already seen a noticeable decrease in memory and CPU util. It is easy to compare by sorting by CPU% and there will be the highest qps process.
I'm thinking of starting small as qps, so that everyone contibutors and maintainers can make sure that such optimizations work. And then move on to the more important components lxqt DE.