Web Farm/Web Garden

[Steve]

Hi
What is difference between web farm and web garden?

What i understand so far
Web Farm
Multi Server Environment
Support Session share
Application object not supported
Caching not recommended (??)
What about Page Cache (??)

Web Garden
Multi-Processor Scenario

Rest same as Web Farm

Expert Comments Expected
Regards
Steve

[Elliot M. Rodriguez]

Web garden scenarios, IMHO, are quite uncommon. I havent found anything yet
that a solid server with enough RAM cannot handle.

To me, the only thing to really watch is how you configure webgardens, and
manage session state. In IIS5 you need to modify the machine.config files so
your application can support webgardens (the webgarden and cpumask
attributes). In IIS6 you can modify these settings on a per-application pool
basis using the MMC.

When you implement web gardens, each of the asp.net processes has its
processor affinity assigned to a specific processor. This can result in
sessions values apperaing lost, or empty. Using the session state service or
SQL Server to manage your sessions is better in this case, as both serve as
a single session repository.

In web farming, application objects *are* supported. They haveto be
implemented, though, using either state service or SQL Server for the
reasons mentioned above (single session storage).

You can implement caching for web farms, gardens, etc. under any scenario
using page output caching (varybyparam attribute). This should handle your
page cache question. I have implemented caching, both data and page, on a 5
server web farm without any problems.

With a web farm, you will have to change each machine's machineKey attribute
under machine.config. These must match so each application's viewstate
requests match (otherwise you'll get corrupt ViewState errors). MS has a KB
that applies to the above scenario (and source for an executable that will
build new hash keys) at
http://support.microsoft.com/default...oduct=NETFrame.

MSDN has a lot more detail for your other questions than I could ever
provide to you. but I hope this helps to start.



"Steve" <St***@discussions.microsoft.com> wrote in message
news:1a****************************@phx.gbl...

Hi
What is difference between web farm and web garden?

What i understand so far
Web Farm
Multi Server Environment
Support Session share
Application object not supported
Caching not recommended (??)
What about Page Cache (??)

Web Garden
Multi-Processor Scenario

Rest same as Web Farm

Expert Comments Expected
Regards
Steve

[Gopal Prabhakaran]

Dear All

Can we maintain session accross the webapplication, if so pls help me to do?

(i.e) = I have 2 webapplication namely http://localhost/webapp1 ,
http://localhost/webapp2

Can I use the session created in http://localhost/webapp1 in
http://localhost/webapp2

Pls Help me...
Millions of thanx in advance

--
Thanx
Gopal Prabhakaran

"Elliot M. Rodriguez" <someemail> wrote in message
news:O$**************@TK2MSFTNGP10.phx.gbl...

Web garden scenarios, IMHO, are quite uncommon. I havent found anything yet that a solid server with enough RAM cannot handle.

To me, the only thing to really watch is how you configure webgardens, and
manage session state. In IIS5 you need to modify the machine.config files so your application can support webgardens (the webgarden and cpumask
attributes). In IIS6 you can modify these settings on a per-application pool basis using the MMC.

When you implement web gardens, each of the asp.net processes has its
processor affinity assigned to a specific processor. This can result in
sessions values apperaing lost, or empty. Using the session state service or SQL Server to manage your sessions is better in this case, as both serve as a single session repository.

In web farming, application objects *are* supported. They haveto be
implemented, though, using either state service or SQL Server for the
reasons mentioned above (single session storage).

You can implement caching for web farms, gardens, etc. under any scenario
using page output caching (varybyparam attribute). This should handle your
page cache question. I have implemented caching, both data and page, on a 5 server web farm without any problems.

With a web farm, you will have to change each machine's machineKey attribute under machine.config. These must match so each application's viewstate
requests match (otherwise you'll get corrupt ViewState errors). MS has a KB that applies to the above scenario (and source for an executable that will
build new hash keys) at
http://support.microsoft.com/default...&Product=NETFr
ame.
MSDN has a lot more detail for your other questions than I could ever
provide to you. but I hope this helps to start.



"Steve" <St***@discussions.microsoft.com> wrote in message
news:1a****************************@phx.gbl...

Hi
What is difference between web farm and web garden?

What i understand so far
Web Farm
Multi Server Environment
Support Session share
Application object not supported
Caching not recommended (??)
What about Page Cache (??)

Web Garden
Multi-Processor Scenario

Rest same as Web Farm

Expert Comments Expected
Regards
Steve

[Elliot M. Rodriguez]

It is possible, but IMHO its not a good idea.

Someone did this modifying the SQL Server script that builds the
ASPSessionState database (so this only works with SQL Server session state),
and I dont know how it works, but this is the only thing I found on it:

http://www.codeproject.com/useritems...sion_state.asp

"Gopal Prabhakaran" <pr*******@takescm.com> wrote in message
news:O3*************@TK2MSFTNGP12.phx.gbl...

Dear All

Can we maintain session accross the webapplication, if so pls help me to do?
(i.e) = I have 2 webapplication namely http://localhost/webapp1 ,
http://localhost/webapp2

Can I use the session created in http://localhost/webapp1 in
http://localhost/webapp2

Pls Help me...
Millions of thanx in advance

--
Thanx
Gopal Prabhakaran

"Elliot M. Rodriguez" <someemail> wrote in message
news:O$**************@TK2MSFTNGP10.phx.gbl...

Web garden scenarios, IMHO, are quite uncommon. I havent found anything yet

that a solid server with enough RAM cannot handle.

To me, the only thing to really watch is how you configure webgardens, and manage session state. In IIS5 you need to modify the machine.config files so

your application can support webgardens (the webgarden and cpumask
attributes). In IIS6 you can modify these settings on a per-application pool

basis using the MMC.

When you implement web gardens, each of the asp.net processes has its
processor affinity assigned to a specific processor. This can result in
sessions values apperaing lost, or empty. Using the session state

service or

SQL Server to manage your sessions is better in this case, as both serve as

a single session repository.

In web farming, application objects *are* supported. They haveto be
implemented, though, using either state service or SQL Server for the
reasons mentioned above (single session storage).

You can implement caching for web farms, gardens, etc. under any

scenario using page output caching (varybyparam attribute). This should handle your page cache question. I have implemented caching, both data and page, on a 5

server web farm without any problems.

With a web farm, you will have to change each machine's machineKey attribute

under machine.config. These must match so each application's viewstate
requests match (otherwise you'll get corrupt ViewState errors). MS has a

KB

that applies to the above scenario (and source for an executable that

will build new hash keys) at

http://support.microsoft.com/default...&Product=NETFr ame.

MSDN has a lot more detail for your other questions than I could ever
provide to you. but I hope this helps to start.



"Steve" <St***@discussions.microsoft.com> wrote in message
news:1a****************************@phx.gbl...

Hi
What is difference between web farm and web garden?

What i understand so far
Web Farm
Multi Server Environment
Support Session share
Application object not supported
Caching not recommended (??)
What about Page Cache (??)

Web Garden
Multi-Processor Scenario

Rest same as Web Farm

Expert Comments Expected
Regards
Steve