if your server win2k, then the same asp.net process is hosting all the web
sites, so all sites share the same max memory. also cross site security is
low in this configuration.

if your server win2003/ii6, you can have your site hosted in its own dll
host and and have better memory managment control. cross site security is
still low, but can be improved.

how much impact shared hosting will have depends on the activity or other
sites and your site. if you on a shared web farm is probably better than an
unshared single server.

-- bruce (sqlwork.com)


"George Ter-Saakov" <we@hotmail.com> wrote in message
news:u15i8h7TDHA.1740@TK2MSFTNGP12.phx.gbl...
> Hi.
> It's a bit offtopic.
>
> We are developing .NET application and going to host it on shared server.
>
> Since .NET eats up memory pretty well I am concerned how is it going to
work
> on shared server?
>
> Does anyone has experience with shared hosing? How does it work? Does
hoster
> set a limit on the memory consumed by APP.
> What is happening when that limit is reached? .NET starts the GC? Or is it
> just recycles the process?
>
> No need to give me any specific hoster who you think is the best.
>
> I just want to know does it make sence to run small (about 1 hit a second)
> .NET app from shared hosting?
>
>
> Thanks.
> George.
>
>