Geoff,
I think found what you were referring to. Ft:paginateloop does return
stobjects based on the query passed.
The ft:pagination code is much more efficient than what I was doing
previously.
This rule can display object types with different properties that need to be
rendered, which makes composing the query tough unless I do a select type.*,
which can't be good, especially when I filter it for unique rows using query
of queries. I can probably sort that out by standardizing my teaser
properties.
Is getDisplay() the best method to use in the pagination?
<ft:form action="#pagefu#">
<ft:pagination
currentpage="#url.page#"
maxpages="#iNumberOfPages#"
totalRecords="#qGetData.recordcount#"
recordsPerPage="#stRule.numItems#"
actionURL="#pageFU#"
qRecordSet="#qGetData#"
pagelinks="10"
typename="#stRule.dmType#">
<ft:paginateloop>
<cfset o.getDisplay(stObject=stObject.stobject,
template="#stRule.displayMethod#", alternateText="webskin does not exist")
/>
</ft:paginateloop>
</ft:pagination>
</ft:form>
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] On
Behalf Of modius
Sent: Thursday, August 09, 2007 5:20 PM
To: farcry-dev
Subject: [farcry-dev] Re: Speedup tricks
On Aug 10, 4:34 am, "Derek Westfall" <[EMAIL PROTECTED]> wrote:
> What speed tricks are developers using for sites with large number of
> content objects?
>
> I have a lot of content objects -- around 10,000 I think. Most of them
> will be paginated through with their teasers and thumbnail images showing.
I'm assuming you are only calling objectids in your query, and that you are
only bringing back the records you need to render.
When you make a call to a large number of records and you render them as
straight out views you basically cause a rush on the database as it goes to
grab each record individually, cache within the broker and then display. If
you turned off webskin caching, you should still see a marked improvement in
the performance of the rule as subsequent calls are taken from memory. This
ain't much good if this is a big record set and these objects are seen
infrequently.
You can actually call a special pagination tag that allows you to execute
webskins from a query rather than through fourq. So you populate the query
with the columns that will be used in the webskin.
It then uses the getwebskin stobject argument to bypass the record lookup.
I can't remember of the top of my head the tag call... but let me have a dig
around and see what I can do for you.
-- geoff
http://www.daemon.com.au/
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"farcry-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/farcry-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
