Best practice for long(ish) processes

Discussion in 'ASP General' started by BillAtWork, Oct 12, 2009.

  1. BillAtWork

    BillAtWork Guest

    I'm hoping to find best practices for implementing an process, for
    many 1000's of users, that is mainly "waiting" for data from an external
    service. Platform is c#, IIS, 3.5, sql server 2005. Note that
    processing is mostly taken up waiting for the external web service - the
    actual workload on our side is quite light.

    The process that is called asynchronously from the browser for each user. It
    may take around 10-40 seconds to complete. Note that the user's browser is
    NOT tied up during this time and is not "waiting" for the results - they will
    simply appear upon the user's next refresh of data.

    Is IIS being "tied up" in any way while waiting for this external service? I
    don't think this is about asynchronous calls since the only thing "waiting"
    is IIS. The users are fine. I'm trying to ascertain what's going on when you
    have 1000's of simultaneous processes, each waiting for something. Perhaps
    it's not even an issue and it's just what IIS does for a living!

    Thanks for any help!
    BillAtWork, Oct 12, 2009
    1. Advertisements

  2. Try the ASP.NET group (microsoft.public.dotnet.framework.aspnet) instead of
    here. You will get better answers, as this is the traditional ASP group.

    Peace and Grace,
    Gregory A. Beamer, Oct 12, 2009
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.