Closeing connections

[Ray at]

Hi Croney,

The way I see things if that if you want your page to refresh every minute,
then that is what you should do. If that proves to be more than the
resources you have available can handle, then up the resources. And then
when the reality of the world sets in and you are informed that upping the
resources is not in the budget, then switch to five minutes. What I mean is
that you should not make decisions on the functionality of your application
based on hardware limitations, unless there is no way to get around those
limitations - which is often the case in real life.....

Just make sure that your pages are as efficient as possible. There are many
things you can do to keep overhead down. Aaron has a good FAQ about general
efficiency of ASP pages. Read this, make sure you're doing everything that
is applicable and reasonable, and then go through your code again to see if
you can make it better. [url]http://www.aspfaq.com/2424[/url]

Ray at home

--
Will trade ASP help for SQL Server help


"Croney" <n@n.com> wrote in message
news:0e1d01c35074$c2badb40$a601280a@phx.gbl...

> Hi there.
>
> I have an ifraim included in my default page, which
> displays information pulled from several databases. This
> information scrolled from top to bottom displaying things
> like news, new events and other information. The Main page
> also has queries to databases checking for changes made to
> update the page with an image next to the relating heading
> to advise the user that there is some thing new under that
> heading.
>
> Whiles the main page is not reloaded automatically the
> iframe is.
>
> My question is. When a maxim of 80 users (Intranet) have
> this main page loaded and the iframe being reloaded every
> minute should I close the connection after each connection
> is finish or at the end of all the connections?
>
> There are about 5 connections made for each user which
> could be about 40 users possibly refreshing at the same
> time totaling 200 connections being made at the same time.
>
> I am using IIS5 on Windows200 Server. This server is not
> dedicated to these services and therefore has other
> operations also to handle.
>
> I am thinking of setting it to reload by the clock using
> JavaScript to check for every five minutes and therefore
> all users accessing that page will be updated the same
> time. Instead of setting to reload by counting the time
> that it has been up as this may cause requests being made
> all day long by the users as they view the page at
> different times.
>

[Bob Barrows]

Croney wrote:

> Hi there.
>
> My question is. When a maxim of 80 users (Intranet) have
> this main page loaded and the iframe being reloaded every
> minute should I close the connection after each connection
> is finish or at the end of all the connections?

Ray gave you good advice, but it's hard to tell if he answered your question
(for me anyways), so:
Yes, connections should be opened late and closed early to allow ODBC
Connection Pooling or OLEDB Session Pooling (depending on which you are
using) to work properly This helps keep resource usage down since new
connections don't have to be spawned every time a page requests a
connection. So the less time a page has a connection open, the better chance
that the connection will be used by another thread that needs one. So close
your connections as soon as you are finished with them.

HTH,
Bob Barrows