Inprocess state on multi processor box

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • martin
    #1

    Inprocess state on multi processor box

    Hi,

    I am just about to deploy my production application on a win2k server with
    two processors.

    I have been reading that inprocess session state is not the best method for
    multi processor systems (web garden)
    because asp.net will spawn a single process for each processor.
    I was a little perplexed by this because my dev box has two processors and I
    can't recall an instance of me losing session state.

    also if I am storing my session state inprocess and I make a change to
    web.config in production (say tuen on tracing) then my application will
    restart and reload all settings. does this mean I will lose my inprocess
    session state or will this be retained and only lost in IIS is restarted.

    many thanks in advance.

    Alex.


    Tags: None
    • Rajesh.V
      #2
      Re: Inprocess state on multi processor box

      Any change in webconfig or the app dll will cause the app to restart dumping
      all session state. Use Sql Out of proc for state management if you dont
      want to lose state.

      "martin" <alex_REMOVE_98 76@yahoo.com> wrote in message
      news:ehiSMkHmDH A.2432@TK2MSFTN GP10.phx.gbl...[color=blue]
      > Hi,
      >
      > I am just about to deploy my production application on a win2k server with
      > two processors.
      >
      > I have been reading that inprocess session state is not the best method[/color]
      for[color=blue]
      > multi processor systems (web garden)
      > because asp.net will spawn a single process for each processor.
      > I was a little perplexed by this because my dev box has two processors and[/color]
      I[color=blue]
      > can't recall an instance of me losing session state.
      >
      > also if I am storing my session state inprocess and I make a change to
      > web.config in production (say tuen on tracing) then my application will
      > restart and reload all settings. does this mean I will lose my inprocess
      > session state or will this be retained and only lost in IIS is restarted.
      >
      > many thanks in advance.
      >
      > Alex.
      >
      >[/color]


        Comment

        • Rajesh.V
          #3
          Re: Inprocess state on multi processor box

          Any change in webconfig or the app dll will cause the app to restart dumping
          all session state. Use Sql Out of proc for state management if you dont
          want to lose state.

          "martin" <alex_REMOVE_98 76@yahoo.com> wrote in message
          news:ehiSMkHmDH A.2432@TK2MSFTN GP10.phx.gbl...[color=blue]
          > Hi,
          >
          > I am just about to deploy my production application on a win2k server with
          > two processors.
          >
          > I have been reading that inprocess session state is not the best method[/color]
          for[color=blue]
          > multi processor systems (web garden)
          > because asp.net will spawn a single process for each processor.
          > I was a little perplexed by this because my dev box has two processors and[/color]
          I[color=blue]
          > can't recall an instance of me losing session state.
          >
          > also if I am storing my session state inprocess and I make a change to
          > web.config in production (say tuen on tracing) then my application will
          > restart and reload all settings. does this mean I will lose my inprocess
          > session state or will this be retained and only lost in IIS is restarted.
          >
          > many thanks in advance.
          >
          > Alex.
          >
          >[/color]


            Comment

            Previous template Next
            Working...