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.

Sign up for GitHub

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

Jump to bottom

Performance benchmarking #37

Open
groenroos opened this issue May 9, 2019 · 1 comment
Open

Performance benchmarking #37

groenroos opened this issue May 9, 2019 · 1 comment
Assignees
@groenroos
Labels
help wanted Issues where help is needed from other contributors low priority Issues which should only be considered after everything else is done maintenance Keep dependencies, code and conventions fresh
Milestone
M4 - Release 4.0

Comments

@groenroos
Copy link
Member

groenroos commented May 9, 2019 •
edited

Investigate the best way to benchmark the performance of Sapling, preferably in a way that allows for easy comparison with other similar frameworks. Then, write and run such a benchmark.

Comparison to other frameworks isn't strictly necessary or even useful, as Sapling's focus is not the best possible performance, but speed of development - this will almost necessarily come at a small cost of performance, and developers looking for the most performant framework would probably want to look elsewhere.
@groenroos groenroos added maintenance Keep dependencies, code and conventions fresh low priority Issues which should only be considered after everything else is done help wanted Issues where help is needed from other contributors labels May 9, 2019
@groenroos groenroos added this to the M2 - Release 2.0 milestone May 9, 2019
@groenroos groenroos self-assigned this May 9, 2019
@groenroos
Copy link
Member Author

Would probably want to do this as a GitHub Action, so it can be measured how each PR improves/degrades performance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@groenroos groenroos

Labels
help wanted Issues where help is needed from other contributors low priority Issues which should only be considered after everything else is done maintenance Keep dependencies, code and conventions fresh
Milestone
M4 - Release 4.0
Development

No branches or pull requests
1 participant
@groenroos