Reducing request queuing on ASP.Net / IIS
If you’re hosting an ASP.Net website on Microsoft IIS, you’ve likely seen requests being queued from time to time.
Luckily one of the more common causes is easily remedied, here’s how to do it.
If you’re hosting an ASP.Net website on Microsoft IIS, you’ve likely seen requests being queued from time to time.
Luckily one of the more common causes is easily remedied, here’s how to do it.
Having just updated my Synology DS213j to DSM 5.0 I discovered that new media files were no longer being indexed.
This in turn meant my DLNA was worthless, since new content would never index and thus never show.
Apparently this issue only occurs when you have encrypted at least one shared folder (even though it’s not used for media files, and not configured to be indexed)
Synology has yet to come up with a proper fix for this, so until they do you can fix it like this:
Our content server occasionally responds 503 Server Fault on all requests for about a minute or so.
This seem to occur at random intervals for no apparent reason.
After countless hours we finally found the solution…
One of our servers started showing this error: “Event log service is unavailable. Verify that the service is running.”
Fixing it proved quite simple, after a lot of searching on google…
NowSMS can sometimes pop the error “Unable to access modem at COMx: — Error 5 — Access Denied — Another application is already using this device”
This can happen even though nothing is using the modem…
Here’s how to fix the problem 🙂
Having an IIS serve static content is an excellent idea, however out-of-the-box it performs horribly for the job.
Read here how to archive a factor 20 improvement of the performance, by doing nothing but configuration.