-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New Backend, HDF5_01 - Optimizations for large fixed size arrayset schemas. #160
New Backend, HDF5_01 - Optimizations for large fixed size arrayset schemas. #160
Conversation
Hey @hhsecond this is a first draft PR here.. It's ready for a high level review, but will definitely need some work before thinking about merging it. |
Codecov Report
@@ Coverage Diff @@
## master #160 +/- ##
==========================================
- Coverage 95.31% 95.14% -0.17%
==========================================
Files 64 65 +1
Lines 11548 11821 +273
Branches 977 1023 +46
==========================================
+ Hits 11006 11246 +240
- Misses 361 384 +23
- Partials 181 191 +10
|
f562d36
to
38f5df2
Compare
@elistevens this will interest you. Once this is merged (hopefully in the next few days) I'll be pushing v0.4.0b1 |
5b7a483
to
9a2f406
Compare
4afb38b
to
c30f326
Compare
40f5545
to
d6a9bfd
Compare
…rethink how we express what each backend is optimized for during selection
… is not a PR which should introduce changes to that particular backends performance
…erizations and fixtures
d6a9bfd
to
368f5eb
Compare
368f5eb
to
9167eee
Compare
This pull request fixes 16 alerts when merging 9167eee into d105e56 - view on LGTM.com fixed alerts:
|
Motivation and Context
Why is this change required? What problem does it solve?:
Significant performance improvements for larger fixed size arrayset data.
Inline documentation explains rationale.
If it fixes an open issue, please link to the issue here:
Description
Describe your changes in detail:
HDF5_01
backend (to complementHDF5_00
).Types of changes
What types of changes does your code introduce? Put an
x
in all the boxes that apply:Is this PR ready for review, or a work in progress?
How Has This Been Tested?
Put an
x
in the boxes that apply:Checklist: