|
Recent
Articles |
SEO-Friendly Ecommerce
One of the major drawbacks when taking the dynamic approach to web development is the resulting product not being optimized for the search engines. A number of issues contribute to this characteristic and most are them are correctable, but doing so is considered an advanced level of web design.
SES Session: Fun With Dynamic Sites
The idea that your site has to be static, or look static, to do well in search engines is getting to be a thing of the past. This session covered the myths and current issues that people are facing with dynamic websites. All of which can be fixed. Things to consider - ? in a URL is ok....
Is My Perl, CGI, MYSQL Site Obsolete?
That is the question that one person asks in the web programming discussion forum at WebProWorld. Member ericjw says: I am not a back-end person, but I try my hardest to understand. I have recently been considering a phase 2 design for our site. It's a match-making style website in a niche industry. I had several programmers....
Enterprise 2.0 in a Box
A small dream of mine came true. We've been preaching an ecosystem of tools for some time now. We've helped customers stitch them together in interesting ways. In fact, Andrew McAfee's original article on Enterprise 2.0 was borne from observing what was happening in one of our customers and projecting...
Using External JavaScript Source Files
By now most web designers and developers know that JavaScript causes a real headache for search engine spiders. There are however a number of scripts which, whilst not absolutely essential to the functioning of a site, are nevertheless very handy. So where do...
|
|
|
12.27.06
How Many Rows Of Data To Use With Spry
By Raymond Camden
Bob sent in an interesting email to me:
Ray, we're about to use spry on one of our sites but i was wondering what you would recommend to be the max records to return in the XML? We may have 2,000 records returned at a time (in a directory format)?
Do you have any performance tips etc.
When it comes to determining how many rows of data should be returned, you can't just focus on the number of rows. You must also consider the size of each row. So imagine a set of XML that had one column per row:
<people>
<name>Jack Abbot</name>
<name>Victor Newman</name>
<name>Nick Newman</name>
</people>
In the example above the XML only contains the person's name. If it contained other information (gender, age, marital status, salary, etc), then the size of the XML dramatically increases with each row.
So the first thing you want to do is get a gut feeling for the size of your rows.
Next you want to figure out how long its taking for the browser to load your XML.
The best tool for that (well, for Firefox users) would be Firebug. It lets you trace AJAX requests.
This includes the URL, the response, and important to you in this post is the time it took to load. If you can't use Firebug, you should also look at ServiceCapture.
I actually use them both as ServiceCapture is great for monitoring Flash Remoting requests.
One of these days I'm going to get together a simple demo showing how to combine client side paging and server side paging to handle very large data sets in Spry.
Comments
About the Author:
Raymond Camden, ray@camdenfamily.com
http://ray.camdenfamily.com.
Raymond Camden is Vice President of Technology for roundpeg, Inc. A long
time ColdFusion user, Raymond has worked on numerous ColdFusion books
and is the creator of many of the most popular ColdFusion community web
sites. He is an Adobe Community Expert, user group manager, and the
proud father of three little bundles of joy.
|
