news:1157670193.929667.89040@b28g2000cwb.googlegroups.com...
> Hello everyone,
>
> I've run into a peculiar road-bump that I'm hoping someone can clarify.
>
> I'm building a database application (ASP.NET 2.0, MSSQL 2000) and have
> implemented data source caching via polling without a problem.
> Basically what I have is a GridView bound to an ObjectDataSource that
> is calling a query that returns thousands of records. My goal is to
> quickly page through the GridView.
>
> With no caching the page takes 2-3 minutes to load. Data source caching
> reduces the time to 2-3 seconds. Then I Atlas-enabled the page and the
> load time jumps up to roughly 30 seconds.
>
> My question is: Are there any known issues with caching with Atlas? I
> tried Googling around and checking my usual sources and can't seem to
> find any relevant discussion on the two. Am I missing something?
>
> Thanks!
> Jeff
>

> First, be sure that caching is the real issue. There are other things that
> can slow down an Atlas (or Ajax) call. It could be the Atlas libraries
> themselves (this can be tested with another implementation, like Ajax.Net,
> etc.). It could be a network latency issue (move to a closer machine). It
> could be your machine is overloaded (check the memory, cpu, etc. or move to
> another machine).
>
> You are going to add some overhead using any type of Ajax implementation. It
> is possible that the default caching, with Atlas, is an issue (have not
> tried personally). If so, you can implement another caching solution to
> speed things up.
>
> The last question you have to deal with is whether you need Atlas or not.
> The main reason to Ajax enabled an application is to improve user experience
> (help a user fill in forms, etc.). It should not become a substitute data
> transport mechanism, as you end up having to support two mechanisms. While
> you might still end up with a simple enough transport through the marriage,
> once you step out of the box, you end up with little reuse, which is not as
> maintainable. While I would still investigate this issue, I would not be
> opposed to a full postback if it is returning much faster than the Atlas
> enabled paging.
>
> --
> Gregory A. Beamer
> MVP; MCP: +I, SE, SD, DBA
>
> *************************************************
> Think outside of the box!
> *************************************************
> <jeffmag***@gmail.com> wrote in message
> news:1157670193.929667.89040@b28g2000cwb.googlegroups.com...
> > Hello everyone,
> >
> > I've run into a peculiar road-bump that I'm hoping someone can clarify.
> >
> > I'm building a database application (ASP.NET 2.0, MSSQL 2000) and have
> > implemented data source caching via polling without a problem.
> > Basically what I have is a GridView bound to an ObjectDataSource that
> > is calling a query that returns thousands of records. My goal is to
> > quickly page through the GridView.
> >
> > With no caching the page takes 2-3 minutes to load. Data source caching
> > reduces the time to 2-3 seconds. Then I Atlas-enabled the page and the
> > load time jumps up to roughly 30 seconds.
> >
> > My question is: Are there any known issues with caching with Atlas? I
> > tried Googling around and checking my usual sources and can't seem to
> > find any relevant discussion on the two. Am I missing something?
> >
> > Thanks!
> > Jeff
> >