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

Missing/Broken link for benchmarks in 'Going big with Datalad' section #797

Closed
Myrskyta opened this issue Dec 15, 2021 · 9 comments · Fixed by #807
Closed

Missing/Broken link for benchmarks in 'Going big with Datalad' section #797

Myrskyta opened this issue Dec 15, 2021 · 9 comments · Fixed by #807

Comments

@Myrskyta
Copy link

There is a a broken link in the section 2.1.1.2. found at book/docs/beyond_basics/101-160-gobig.rst

The text reads:

If you are interested in up-to-date performance benchmarks, take a look at www.datalad.org/test_fs_analysis.html. This can help >to set expectations and give useful comparisons of file systems or software versions.

I did end up finding the old version for the link, but I am unsure if this was intentionally removed or not from the main site.

@welcome
Copy link

welcome bot commented Dec 15, 2021

Welcome Banner (Image: CC-BY license, The Turing Way Community, & Scriberia. Zenodo. http://doi.org/10.5281/zenodo.3332808) Hi there, and welcome to the DataLad Handbook! 📙 👋 Thank you for filing an issue. We're excited to have your input and welcome your idea! 😊 If you haven't done so already, please make sure you check out our Code of Conduct.

@adswa
Copy link
Contributor

adswa commented Dec 15, 2021

Thanks a lot for the report! Indeed, we redid the website, and this page is gone. Just for the record, in case you were interested in those (by now probably outdated) benchmarks, the sources for the old page are here: https://github.com/datalad/datalad.org/blob/92649aba9ba80221fafea467ffc990ce6c6d2cd9/content/pages/test_fs_analysis.html

@yarikoption, do you still maintain a source of benchmarks across file systems etc. that I could link by any chance? Else, we'll need to strip that sentence.

@all-contributors please add @Myrskyta for bug

@allcontributors
Copy link
Contributor

@adswa

I've put up a pull request to add @Myrskyta! 🎉

@adswa
Copy link
Contributor

adswa commented Jan 10, 2022

oh I didn't realize I mistyped @yarikoptic 's github handle 🤦

@yarikoptic do you still maintain a source of benchmarks across file systems etc. that I could link by any chance? Currently, there is a broken link in the handbook to datalad.org, where we used to report those benchmarks, but this page doesn't exist anymore with the website update from December. If there is nothing, I need to strip that sentence.

@yarikoptic
Copy link
Contributor

yeap, seems was removed in datalad/datalad.org@233cb18 . Source is still in the history of git and could be recovered. I do not remember if I have a separate instance of it published anywhere. It would be nice to reincarnate it (attn @jsheunis) -- I had referenced that page in a good number of locations and AFAIK it is somewhat unique, albeit dated. With @aqw we had hopes to redo it with more modern implementations of ZoL and BTRFS but never had that extra time.

@jsheunis
Copy link
Contributor

Sorry, I missed this. @yarikoptic created an issue to recover it for the updated website: datalad/datalad.org#113. Will post here once it's updated.

@jsheunis
Copy link
Contributor

This page has been restored in datalad/datalad.org#116 and is available on the new site: http://www.datalad.org/test_fs_analysis.html

@adswa
Copy link
Contributor

adswa commented Feb 17, 2022

Great thanks! #807 will bring it back into the book.

@adswa
Copy link
Contributor

adswa commented Oct 19, 2023

hey @Myrskyta! I have a random question: Everyone who contributes to this book is a co-author on the PDF version. I'm currently going through the contributor list, and ask people who are named with their github handles whether they want to appear with their real name. If you want any other name than Myrskyta on it, feel free to ping me here :) Otherwise, feel free to ignore this. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants