Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

application run so slowly the first time

Status
Not open for further replies.

taree

Technical User
May 31, 2008
316
US
We have an application developed by the consultant. When the application run the first time it takes forever to return records since it is a lot of recrods returning. After it runs and returns the first record the application seem to run fast. My concern is it is going to be a turn off for management when they see how slow it is the first time. We have over 10000 records and the list is growing. what can the consultant do to make the application run faster at first time.

thank you
 
Perhaps some sort of screen at startup to enter criteria for initial retrieval before doing it. Warning if no criteria are entered with a "Are you sure? this may take some time..."

John
 
There is Abosultly no reason to return 10000+ records for any reason. as John suggested, have some input fields to filter the criteria.
I for some ridiculous reason they want all rows, then impliment custom paging, not default(built in paging)
 
the system is most likely querying all the data the first time and storing the data in some form of cache. additional hits will filter the cached values instead of issuing another page. at a minimum there should be a paging solution (and not the default paging provided by webforms controls, you will hit the same problems). this would limit the maximum number of records returned from the database to a single page (20 - 50 records).

a minimum of 2 queries will be issued.
1. the page of results
2. the total counts of items.
I am confidant this alone would reduce latency.

from there I would examine 2 other aspects:
1. system preformance with a tool like dotTrace. this will inform you of bottlnecks in code.
2. query execution plans. this will tell you where problems lie in accessing the data.
these can be analyzed independent of one another.

chances are this was missed earlier in the development cycle because the system was never stress tested. for future endeavors this should be part of acceptance testing.

Jason Meckley
Programmer
Specialty Bakers, Inc.

faq855-7190
faq732-7259
 
I will pass it on see if what better way they can come up with to fix this issue. Believe me sometimes I feel like throwing the pc out of the window b/s it is exteremly slow.I will update you guys with the final outcome ....thank you
 
Just remember to ensure if you go for the screen to enter criteria at the beginning, that appropriate indexes are in place on the data tables to not just postpone the big select.

John
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top