Skip to content
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

Comparing on-disk and in-memory backends #165

Closed
lgatto opened this issue Oct 10, 2016 · 1 comment
Closed

Comparing on-disk and in-memory backends #165

lgatto opened this issue Oct 10, 2016 · 1 comment
Labels

Comments

@lgatto
Copy link
Owner

lgatto commented Oct 10, 2016

The benchmarking vignette documents the differences in terms of timings and RAM usage, but there is actually much more. While we want to make sure the the two back-end keep the same API (or at least as much as possible), there are fundamental differences, including

MS levels

on-disk support multiple MS levels in one object, while in-memory only supports a single level. While support for multiple MS levels could be added to the in-memory back-end, memory constrains make this pretty-much useless and will most likely never happen.

Serialisation

in-memory objects can be save()ed and load()ed, while on-disk can't. As a workaround, the latter can be coerced to in-memory though. We would need mzML write support in mzR to be able to implement serialisation for on-disk data.

@lgatto
Copy link
Owner Author

lgatto commented Jan 20, 2017

This has been added to the benchmarking vignette.

@lgatto lgatto closed this as completed Jan 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant