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
{{ message }}
This repository has been archived by the owner on Apr 22, 2023. It is now read-only.
When process.env.NODE_DEBUG is not defined, then in lib/http.js the debug function is defined as function () { } (line 35). Nonetheless, in OutgoingMessage.prototype.write it calls debug as: debug('string chunk = ' + util.inspect(chunk)) (line 612), thus even when debug is disabled util.inspect() is being called, after profiling I found that my application was spending a considerable amount of time in util.inspect(). Fixing this bug resulted in a considerable performance improvement.
The text was updated successfully, but these errors were encountered:
When process.env.NODE_DEBUG is not defined, then in lib/http.js the debug function is defined as
function () { }
(line 35). Nonetheless, in OutgoingMessage.prototype.write it calls debug as:debug('string chunk = ' + util.inspect(chunk))
(line 612), thus even when debug is disabled util.inspect() is being called, after profiling I found that my application was spending a considerable amount of time in util.inspect(). Fixing this bug resulted in a considerable performance improvement.The text was updated successfully, but these errors were encountered: