`bin/tapioca gem --verify` significantly slower on 0.9.2 (vs 0.8.3)
We recently updated tapioca from 0.8.3 to 0.9.2 and it looks like the bin/tapioca gem --verify command we run on CI is now about 2x slower.
It seems like it used to usually take under 2 mins to run in CI, and it now regularly takes more than 4 mins.
Let me if there's more information I can share.
@pjambet if you can help you, can you try to narrow down to just one single release of tapioca. For example, is 0.9.1 also as slow as 0.9.2? That way we can find which release introduced the slowdown.
@rafaelfranca I'll give this a shot this afternoon and update with my findings.
@rafaelfranca I tried 0.9.0 & 0.9.1 and both show similar times as 0.9.2 (4m31s & 4m44s respectively). Also ran a control run on 0.8.3 one more time, and it ran in 2m4s. So it does seem to point at 0.9.0 as the version introducing the slowdown.
Just ran a similar test on the most two recent versions, 0.9.3 & 0.9.4 and saw similar "slow" types as observed since 0.9.0, respectively 5m20s and 6m46s
@pjambet do you mind trying this out with the newest Tapioca release and letting us know how it affects execution time on your application?
@dirceu Just finished running a few builds on 0.10.0, 0.10.1 & 0.10.2 and got times that seem to match what we we observing on 0.8.x on the latest version, respectively, 6m50s, 5m56s & 2m15s (actually ran it three times on 0.10.2 and got 2m32s & 2m25s)
So it does look like 0.10.2 solved our issues!
Thanks for testing that (and for original reporting this); I'm glad to hear it's fast enough for your case!
There's still some investigation and benchmarking to be done on Tapioca in general, but I'll open a separate issue for that.