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

add documents about test, benchmark, plotting and utility scripts #24

Open
grafi-tt opened this issue Jan 1, 2019 · 2 comments
Open
Assignees

Comments

@grafi-tt
Copy link
Owner

grafi-tt commented Jan 1, 2019

Some usage information should be added.

I'm satisfied with current provisioning, tests and benchmark chain, written in POSIX shell script and Lua. Using unit-test library like Busted and/or provisioning tool like Ansible would be more modern, but this is Lua world, where minimalism is appreciated. Surely, I want to add Windows support, but I want to keep busybox support as well.

For plotting, YAML-formatted benchmark results are generated by Lua. It is converted to gnuplot input by a Ruby script. Changing the intermediate format to JSON and using Lunajson itself for plotting have some beauty, but who cares. I want to escape from Python at a hobby-project, because I'm working on so-called "data science" for a living.

@grafi-tt grafi-tt self-assigned this Sep 13, 2020
@grafi-tt
Copy link
Owner Author

grafi-tt commented Sep 14, 2020

Now Lunajson uses matplotlib to plot benchmark results. Benchmark procedure is simplified and automated. (I hadn't personally liked Python, but now I'm forgetting Ruby...)

I'll add some docs about testing and benchmark to README

@tst2005
Copy link
Contributor

tst2005 commented Sep 22, 2020

Minor: typo in issue title: s/docuements/documents/

@grafi-tt grafi-tt changed the title add docuements about test, benchmark, plotting and utility scripts add documents about test, benchmark, plotting and utility scripts Nov 5, 2023
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

No branches or pull requests

2 participants