Skip to content

Codepolice

  • ⤫

New Relic and runAllManagedModulesForAllRequests flag in .net

Posted by Judy Alvarez Posted on February 25, 2022March 1, 2022
0

I have been playing around with the awesome performance measuring tool New Relic lately and have been struggling with some performance issues that would have been hard to find without measuring the actual metrics from the real production server.

Anyway, during the different changes, I made I changed the option runAllManagedModulesForAllRequests from “true” to “false” in Web. Config and all of a sudden I got much worse numbers from New Relic compared to before this change. That was pretty weird since everyone said that this should be off for performance reasons.

Pretty soon I realized that the reason that the numbers got worse was that it stopped measuring the performance of scripts, style sheets, and images which of course is fast.  Now I will continue with the mystery of the “System.Web.Handlers.TransferRequestHandler” method that is making my app slower for some reason.

Update Check this thread on Stack Overflow for some more info about the System.Web.Handlers.TransferRequestHandler problem.

Categories: JavascriptTagged: asp net advantages, asp net blazor, asp net calendar control, asp net checkboxlist, asp net core angular, asp net core routing, asp net core version, asp net core web api interview questions, asp net course, asp net mvc framework, asp net mvc vs asp net core, asp net pdf, asp net repeaters, asp net templates, asp net tutorial mvc, asp net vs mvc, asp net web application development, asp net webhosting, authentication and authorization in asp net, autopostback in asp net, custom control in asp net, custom validator in asp net, difference between asp and asp net, difference between asp net and mvc, difference between net and asp net, forms authentication in asp net, login page in asp net, repeater control in asp net, web config in asp net, what is asp .net

Post navigation

Previous Previous post: 404 redirects in code with ASP.NET
Next Next post: Problems with MSBUILD tasks after playing with Visual Studio 

Related Posts

  • What’s next for JavaScript frameworks in 2026

    #​770 — January 27, 2026 Read on the Web JavaScript Weekly Introducing LibPDF: PDF Parsing and Generation from TypeScript — LibPDF bills itself as ‘the PDF library TypeScript deserves’ and supports parsing, modifying, signing and generating PDFs with a modern API in Node, Bun, and the browser. GitHub repo. Documenso JavaScript Frameworks – Heading into 2026

    Posted by Posted on January 27, 2026
    0
  • require(esm) now stable in Node 25

    #​608 — January 22, 2026 Read on the Web Node.js 25.4.0 (Current) Released — Another gradual step forward for Node with require(esm) now marked as stable, as well as the module compile cache, along with a variety of other minor tweaks. Joyee Cheung of the Node team has written a thread on Bluesky going deeper

    Posted by Posted on January 22, 2026
    0
  • A big week for jQuery

    #​769 — January 20, 2026 Read on the Web JavaScript Weekly jQuery 4.0 Released — 20 years on from its original release, the ever-popular (in terms of actual usage) library reaches 4.0 with a migration to ES modules (compatible with modern build tools) along with dropping support for IE 10 and older. With jQuery being

    Posted by Posted on January 20, 2026
    0
  • A new guide to configuring Node packages

    #​607 — January 15, 2026 Read on the Web ⚠️ The Node.js January 13, 2026 Security Releases — Originally expected in December, these releases (of Node.js 25.3.0, 24.13.0, 22.22.0, and 20.20.0) finally landed this week, largely due to their complexity and the scope of the vulnerabilities they tackle. More on that in the next item! The Node.js

    Posted by Posted on January 15, 2026
    0
  • Can we ever fix the web dependency mess?

    #​768 — January 13, 2026 Read on the Web JavaScript Weekly Web Dependencies are Broken; Can We Fix Them? — Lea, who has worked at the heart of Web Standards for years, delivers a compelling (and educational) call to action about a problem every JavaScript developer has encountered: why is managing dependencies and introducing them

    Posted by Posted on January 13, 2026
    0
  • The story of how require(esm) became stable

    #​606 — January 8, 2026 Read on the Web 🎉 Happy New Year! Also, a quick reminder that Node Weekly is now sent every Thursday as part of a reshuffle for many of our newsletters. __Your editor, Peter Cooper npm to Implement ‘Staged Publishing’ After Turbulent Shift Off Classic Tokens — 2025 was a tricky year

    Posted by Posted on January 8, 2026
    0
Judy Alvarez

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Codepolice

  • Github
  • Atlassian
  • Flatlogic
  • Xero
  • Jetbrains
  • Figma
  • What’s next for JavaScript frameworks in 2026
  • require(esm) now stable in Node 25
  • A big week for jQuery
  • A new guide to configuring Node packages
  • Can we ever fix the web dependency mess?
https://flatlogic.com/generator
COPYRIGHT © 2026 - Codepolice