You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@wallin This is still relevant. We hit this footgun using the class method in a rails request - loading the yaml and compiling the regexes on every request. This added about 40-50ms per-request, which is quite unexpected and one of those things that's really easy to miss when you first introduce using this gem - though I appreciate the readme does attempt to address it.
If the docs clearly stated "Expect this method to take 50ms" I suspect nobody would use it. I support this issue.
Activity
wallin commentedon Jun 13, 2017
@toolmantim Is this still relevant?
soulcutter commentedon Sep 16, 2021
@wallin This is still relevant. We hit this footgun using the class method in a rails request - loading the yaml and compiling the regexes on every request. This added about 40-50ms per-request, which is quite unexpected and one of those things that's really easy to miss when you first introduce using this gem - though I appreciate the readme does attempt to address it.
If the docs clearly stated "Expect this method to take 50ms" I suspect nobody would use it. I support this issue.
AxelTheGerman commentedon Oct 19, 2023
First step could be to add a deprecation warning maybe? That could already educate and also help transition.