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

Criterion Benchmarks #7

Open
athanclark opened this issue Dec 21, 2014 · 0 comments
Open

Criterion Benchmarks #7

athanclark opened this issue Dec 21, 2014 · 0 comments
Assignees
@athanclark
Labels
feature request goal ready

Comments

@athanclark
Copy link
Owner

Bench some weights and get beefy.

It's most important for us to test strict and lazy Text, so we'll stick our stringy types to those. We should be pretty imaginative in how many ways this could be done:

  • comparing deployments
  • relative deployment vs. raw showing
  • constant time showing
  • tough: work with Lucid - see raw vs. UrlString's - hopefully there's no bottleneck at renderTextT.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@athanclark athanclark

Labels
feature request goal ready
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@athanclark