Merged
Conversation
added 23 commits
April 24, 2025 08:37
… fixed an issue for initialization of map of files to handle in memory
This commit fixes the read operation when file is stored in memory. TODO: fix as soon as possible the ReadRequestCacheMEM class, as right now it might contain bugs somewhere that are not clear. Also some varibles can be removed
Caches now work independently of size. Increased posix read cache line size to 32K of data
Since caches are used to improve performance for small size IO operation, when a read() operation that targets a size greater than the size of the read cache line size is issued, the cache is being bypassed and the read operation occurs directly from the shared memory segment.
d668929 to
f7bc6bf
Compare
84570bd to
c9ab329
Compare
a969efc to
2718483
Compare
added 2 commits
May 6, 2025 13:47
5dc7178 to
18d4ef6
Compare
18d4ef6 to
1f88af1
Compare
added 4 commits
May 12, 2025 14:23
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## capio-v2 #135 +/- ##
============================================
+ Coverage 47.46% 51.41% +3.94%
============================================
Files 71 71
Lines 3339 3637 +298
Branches 1913 2099 +186
============================================
+ Hits 1585 1870 +285
+ Misses 865 844 -21
- Partials 889 923 +34 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
marcoSanti
pushed a commit
that referenced
this pull request
Jun 22, 2025
- Fixed mechanism to send memory storage regex - Added flag to store everything in memory - Added request for memory file in init_client() - Fixed an issue in return value for posix in memory write handler, and fixed an issue for initialization of map of files to handle in memory - Fixed write in memory for simple test - Fix on writev - Fix on cache wrong bytes. TODO: fix wrong read size - Completed IO operations on single machine - Added test for read and write in memory file. broken when reaching 1.3MB of data - Bugfix on offset calculation in capio memory file - Fixed reads on different mem pages - Fixed custom cache line size issues - Caches now work independently of size. Increased posix read cache line size to 32K of data - Improved test with bandwidth data - Performance improvement for data transfer: Since caches are used to improve performance for small size IO operation, when a read() operation that targets a size greater than the size of the read cache line size is issued, the cache is being bypassed and the read operation occurs directly from the shared memory segment.
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
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.
This merge brings back the option to store the files inodes inside the CAPIO main memory. The mechanism can be used in two different ways:
This commit also adds tests to check capio server storage service, as well as bandwidth in both read and write.