Suppose a public WebApp is hosted on an EXtra Small (XS) Azure Virtual Machine (VM). What benefits and/or performance problems might visitors experience if a Memory-Resident Virus Scanner is run on that VM?

1 Answer 1


they would experience a detriment to response time relative to your VM resources. Beyond that its a guess question. "Some detriment, what specifically is unknown without VM environment specifics"

Lousy albeit concise answer. If you would like a more concrete answer: avail us to more concrete server resource information :D

Good luck sir or madam ! :D

  • Right now, the Azure Price calculator seems to imply that an XS Azure VM behaves like a 1GHZ GPU of unknown architecture with 768 MB of RAM. The WebApp would be MVC and probably use few resources, but I might be tempted to load the XS VM down with an instance of SQL Server 2008 Express with no reporting services. I’m wondering if I manually scan most of the content before making it publically available, do I really need the additional overhead of a Virus Scanner to protect visitors.
    – Shawn Eary
    Jan 4, 2013 at 4:37
  • ok ambiguity question : "I'm wondering if I scan most WebApp content " --- do you mean "each request processed by the webapp" or is there some form of user submission process you are particularly interested in ? Jan 4, 2013 at 4:39
  • If a user legally submits a picture or MP3 file to me that she/he created, then perhaps I can scan it on a workstation before allowing everyone else to access it on the server. I would really like to avoid scanning every file access on the webserver via a modern day Virus Scanner since I suspect that would choke an XS Azure VM instance.
    – Shawn Eary
    Jan 4, 2013 at 4:46
  • 1
    ok so the assumption at this point is your user's submission will interact with a servlet or something similar which will invoke validation methods / processes. With the assumption that you are using your own antivirus exam OR an external (3rd party) exam - the important part is to acknowledge to the user that the file has been received and is "being processed" (not much unlike Youtube's ) --- therein fork processing to a lesser priority and user experience is maintained as well as security. Threading is important to robust applications Jan 4, 2013 at 4:50
  • 1
    if you properly fork the processing of files, then you can additionally send the "confirmation" note to end users once the file is processed. In the case of an "image" that seems unnecessary - but if you are dealing with large files in varying formats - you should really just create a trigger to an antivirus application on submission of said file(s) and its actually quite lean on server resources (prioritization is key) . Jan 4, 2013 at 5:01

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.