By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
444,078 Members | 1,733 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 444,078 IT Pros & Developers. It's quick & easy.

Optomise for Speed or refresh - performance question?

P: n/a

What is considered best when doing an application that allows you to browse
data eg by month?

I've currently got an app working so it does a complete refresh when you
change the month you are looking at, using a providers SDK tools. This is
reasonably effective - but there is a few seconds on jumping between one
month and the next (having optomised the rest of the app).

However I could change it to only refresh on command, and catch all the data
on first load. This might make the month jumps considerably easier and
smoother.

What is best? Allow for refresh or allow for speed?
I don't really fancy rewriting it all to force refresh (the data only
catches between a limited boundary so as it is currently, it doesnt get ALL
the data, only what is in the necessary time frame for the view).

Would most users prefer to see all the current data without ever having to
refresh, or is the performance loss to much of a sacrifice?

Is it likely as I anticipate to improve the performance by no end (the rest
of the code doesnt do that much except refer to the dataset caught from
xml).

Many thanks
Nov 21 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
Antoine,

Is this a Windows or Web application?

How often would the typical user view the data each day? Once, twice, or
over and over again?

How many records are there in a complete month's worth of data?
--
Mike

Mike McIntyre
Visual Basic MVP
www.getdotnetcode.com

"Antoine" <mf****@dsl-spam.pipex.com> wrote in message
news:10*************@corp.supernews.com...

What is considered best when doing an application that allows you to
browse
data eg by month?

I've currently got an app working so it does a complete refresh when you
change the month you are looking at, using a providers SDK tools. This is
reasonably effective - but there is a few seconds on jumping between one
month and the next (having optomised the rest of the app).

However I could change it to only refresh on command, and catch all the
data
on first load. This might make the month jumps considerably easier and
smoother.

What is best? Allow for refresh or allow for speed?
I don't really fancy rewriting it all to force refresh (the data only
catches between a limited boundary so as it is currently, it doesnt get
ALL
the data, only what is in the necessary time frame for the view).

Would most users prefer to see all the current data without ever having to
refresh, or is the performance loss to much of a sacrifice?

Is it likely as I anticipate to improve the performance by no end (the
rest
of the code doesnt do that much except refer to the dataset caught from
xml).

Many thanks

Nov 21 '05 #2

P: n/a
Hi Thanks for your question

Web app, but as in Intranet mostly

How often? Hard to say. As and when required most likely.

Number of records? As many as they have entered on the activities..

Cheers
Antoine
"Mike McIntyre" <mi****@dotnetshowandtell.com> wrote in message
news:un*************@TK2MSFTNGP11.phx.gbl...
Antoine,

Is this a Windows or Web application?

How often would the typical user view the data each day? Once, twice, or
over and over again?

How many records are there in a complete month's worth of data?
--
Mike

Mike McIntyre
Visual Basic MVP
www.getdotnetcode.com

"Antoine" <mf****@dsl-spam.pipex.com> wrote in message
news:10*************@corp.supernews.com...

What is considered best when doing an application that allows you to
browse
data eg by month?

I've currently got an app working so it does a complete refresh when you
change the month you are looking at, using a providers SDK tools. This is reasonably effective - but there is a few seconds on jumping between one
month and the next (having optomised the rest of the app).

However I could change it to only refresh on command, and catch all the
data
on first load. This might make the month jumps considerably easier and
smoother.

What is best? Allow for refresh or allow for speed?
I don't really fancy rewriting it all to force refresh (the data only
catches between a limited boundary so as it is currently, it doesnt get
ALL
the data, only what is in the necessary time frame for the view).

Would most users prefer to see all the current data without ever having to refresh, or is the performance loss to much of a sacrifice?

Is it likely as I anticipate to improve the performance by no end (the
rest
of the code doesnt do that much except refer to the dataset caught from
xml).

Many thanks


Nov 21 '05 #3

P: n/a
I have found this but I am not sure on some of the points, like whether data
caching would make sense or not. Perhaps I dont need datacahcing and I just
need to check is postback, and if the dataset is already created just use
that - though I doubt that helps with reusing session data on subsequent
session does it?
I have just tried triming the page size. I have viewstate disabled on any
fields I dont need it on and so on.

http://msdn.microsoft.com/library/de...netchapt06.asp
"Mike McIntyre" <mi****@dotnetshowandtell.com> wrote in message
news:un*************@TK2MSFTNGP11.phx.gbl...
Antoine,

Is this a Windows or Web application?

How often would the typical user view the data each day? Once, twice, or
over and over again?

How many records are there in a complete month's worth of data?
--
Mike

Mike McIntyre
Visual Basic MVP
www.getdotnetcode.com

"Antoine" <mf****@dsl-spam.pipex.com> wrote in message
news:10*************@corp.supernews.com...

What is considered best when doing an application that allows you to
browse
data eg by month?

I've currently got an app working so it does a complete refresh when you
change the month you are looking at, using a providers SDK tools. This is reasonably effective - but there is a few seconds on jumping between one
month and the next (having optomised the rest of the app).

However I could change it to only refresh on command, and catch all the
data
on first load. This might make the month jumps considerably easier and
smoother.

What is best? Allow for refresh or allow for speed?
I don't really fancy rewriting it all to force refresh (the data only
catches between a limited boundary so as it is currently, it doesnt get
ALL
the data, only what is in the necessary time frame for the view).

Would most users prefer to see all the current data without ever having to refresh, or is the performance loss to much of a sacrifice?

Is it likely as I anticipate to improve the performance by no end (the
rest
of the code doesnt do that much except refer to the dataset caught from
xml).

Many thanks


Nov 21 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.