Closed ajb closed 9 years ago
We removed a bunch of hacks to YAML that were no longer needed by DJ. These might have been helping your application.
Great to know, thanks for the tip. Will let you know what we find. On Sep 12, 2014 3:51 PM, "David Genord II" notifications@github.com wrote:
We removed a bunch of hacks to YAML that were no longer needed by DJ. These might have been helping your application.
— Reply to this email directly or view it on GitHub https://github.com/collectiveidea/delayed_job/issues/703#issuecomment-55452393 .
https://github.com/collectiveidea/delayed_job/compare/v4.0.2...v4.0.3#files_bucket will give you the changes between the 2 versions
Sorry, I've got that, I'm just wondering about this history of the Psych hacks. I've looked at the blame and file history, but I'm struggling to find the backstory.
All hacks were in place to fix issues with old versions of ruby working with YAML. The hacks that are still there are issues that still exist with current versions of ruby. You can remove the contents of psych_ext and watch things blow up.
None of our hacks were performance related. They were all functionality fixes.
We've also seen a dramatic performance hit for our app when upgrading to 4.0.3. Not just http requests, if I open a rails console and reference one of the models the console hangs for a good 30 seconds before responding. After that it's smooth sailing.
As of 4.0.4 YAML is completely native except when we are loading the job payload. Any performance discussions should be had with the psych gem development team.
Completely understandable. @chrisb87, have you gotten anywhere with understanding where your performance hit is coming from? I'd love to team up and tackle this.
@ajb, I haven't, for now I've just locked my projects to dj 4.0.2
I'm really sorry to file a bug report that's this vague, but I just spent the entire afternoon tracking down a seemingly impossible performance hit of ~400ms in development to a version bump from
4.0.2
to4.0.3
of delayed_job. It's definitely be intention to try and track this down more, but I wanted to post immediately since4.0.3
is only a week old, and others may be running into this.Here's our
Gemfile.lock
after pinning the version to4.0.2
: