dcsimg
Login | Register   
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.


Tip of the Day
Language: SQL
Expertise: Beginner
Mar 24, 1997

WEBINAR:

On-Demand

Application Security Testing: An Integral Part of DevOps


Improving performance

Question:
The repeater in my application seems to be very slow in populating. Is there anything I can do to improve its performance?

Answer:
Poor performance can be the result of a wide number of interacting factors, so to deliver a prescription with so little information would be inaccurate.

That said, I can offer a couple of places to look at for potential problems specifically related to repeaters.

Make sure your RowFetchMode is set to "Fetch As Needed" to avoid fetching all the rows that may eventually end up in the repeater at one time. Of course, if you need all the rows for some type of aggregate total, you will not have this option.

Second, if possible, reduce the number of derived fields that use the SqlLookup() method. Currently, OPO does an individual SQL statement for each lookup, so having three lookups could have some impact on the performance of the repeater.

DevX Pro
 
Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap
×
We have made updates to our Privacy Policy to reflect the implementation of the General Data Protection Regulation.
Thanks for your registration, follow us on our social networks to keep up-to-date