Use Gitlab::Json for render :json calls and uses of ActiveSupport::JSON
What does this MR do and why?
Describe in detail what your merge request does and why.
This provides a notable performance improvement across many areas of the application, by switching Rails' JSON renderer from the default JSON gem to using the Gitlab::Json
class we added previously. Currently this uses the oj
gem instead for dramatic performance gains when parsing or generating JSON.
This MR forces ActiveSupport::JSON
to use our modified subclass instead.
Related #331447
Related #217633 (closed)
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.