Daniel,
That sounds like great work. Can you post individual fixes as seperate
tickets at http://bugs.farcrycms.org/ so they can be considered for
permanent changes to core?
Many thanks,
-- geoff
http://www.daemon.com.au/
Daniel Niklasson wrote:
This is what I've done so far:
1. Added cache to the Container tag
This speeded up things quite a bit as some pages share containers. And on
some pages I wasn't able to use the <skin:cache>. Maybe it's doable but this
container-cache works great and it reduces the number of functions called.
2. Modified fourq and added object-cache
There's an instance-cache implemented today. But as far as I can tell this
is only used if the same instance calls for the same objectid twice in a row
since the structure always only contain one object (the latest accessed by
that instance).
I added my "objectcache" to getData, setData and deleteData. So if a news
item is created for example it's added directly to my cache and when it's
requested on the site the cache is used instantly.
I also cache functionality to findType in the same way as for getData.
3. Optimizing queries
Only looked at ruleNews so far, but replacing maxrows="" with SELECT TOP x
(for SQL Server) and LIMIT for MySql did a lot.
This took me down to below 250 ms for almost every page (with debugging
turned on). If the pages aren't cached the time is cut down to 1/4 of what
it took before.
/ daniel
---
You are currently subscribed to farcry-dev as: [email protected]
To unsubscribe send a blank email to [EMAIL PROTECTED]
Aussie Macromedia Developers: http://lists.daemon.com.au/
