« Previous Next »

Thread: Web gardening while using InProc

Last post 10-18-2009 3:53 AM by stever@bitshop.com. 3 replies.

Average Rating Rate It (5)

RSS

Page 1 of 1 (4 items)

Sort Posts:

  • 09-02-2009, 2:16 PM

    Web gardening while using InProc

    Has there been any improvement to IIS 7 so you can benefit by using both InProc and web gardening?  I would like to spread processing across multiple w3wp workers but don't want to give up InProc speed boost.  Actually I can't use state servers anyway due to several of my objects in session scope are not serializable....plus it's horribly slow....

  • 09-03-2009, 9:18 AM In reply to

    Re: Web gardening while using InProc

    AFAIK there have been no changes to the inProc with gardens.

    As normal when I come across any subject about web garden I have to question what need do you have for this? Do you have multiple queued requests that are not getting processed by the wp?

    I have never considered state servers to be horribly slow there is a small, tiny, even difference. And then you can always sue the SQL server option on a fast machine.

    How many sessions are you talking? to even consider this it must be in the region of tens of thousands of concurrent users.

     

  • 09-04-2009, 9:37 PM In reply to

    Re: Web gardening while using InProc

    None that I know of.  Look at using something like scaleout software or velocity.

    Steve Schofield
    Windows Server MVP - IIS
    http://weblogs.asp.net/steveschofield


    http://www.IISLogs.com
    Log archival solution
    Install, Configure, Forget
  • 10-18-2009, 3:53 AM In reply to

    Re: Web gardening while using InProc

    By definition in proc means in process, using a web garden means multiple processes so in proc would be in that specific process.

    An improvement could be some formula to keep the same people in the same wp, but I would agree generally with the why do this.

    Looking at the code for why you need so much in your session variables is probably a good answer, but of course some apps need different things than others - just saying put less in session vars isn't always an answer.

    Depending on your budget you may want to investigate why you need a web garden - the advantage of a garden is if you have a single / apartment threaded task which blocks other requests - by placing the requests in seperate gardens you generally get around threading issues - Well designed code shouldn't have these kind of issues though. The performance SHOULD be better in one proc instead f the garden.

    There's also an exception on 32 bit of ram but with 64 bit w3wp that is less likely a justification for web gardens.

    Steve Radich - President
    BitShop.com - IIS Cloud Solution Coming Soon - Join our "Free 3 Month Beta" Waiting List Now...
Page 1 of 1 (4 items)
Microsoft Communities