-
Notifications
You must be signed in to change notification settings - Fork 28
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
[ISSUE-68] Improved Specs and Added Coverage Report #70
Conversation
Added coverage report
@mhgbrown Any reason we are maintaining ruby < 3.0? Everything under 3.0 hit EOL Edit: @mhgbrown if you'd consider this I also did the following:
|
1c1c471
to
b2e08ed
Compare
85a7efb
to
dee8057
Compare
No particular reason other than to be most widely compatible. I'm down to move forward and support versions that are "living". |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great stuff and really moves the project forward. I left some questions for you.
It is done. Please review again. @mhgbrown |
I'll get on it later today |
It does more bad than good in real world scenarios. Performance degrades.
|
@jlurena Lawd, sorry. This week suddenly became a week of interviewing/doing a trial at a company. Why remove the concurrency option? |
After research and practical tests, it actually performed really bad. Tested with a redis cache and a memcache cache. Performance degraded significantly. It was visibly slower. @italijancic-th helped test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great!
ok got it! I'll merge it in! |
@jlurena finally released: https://rubygems.org/gems/cached_resource |
Summary