Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We've moved the forum!

Please use forum.silverstripe.org for any new questions (announcement).
The forum archive will stick around, but will be read only.

You can also use our Slack channel or StackOverflow to ask for help.
Check out our community overview for more options to contribute.

Data Model Questions /

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo, swaiba

MySQL Out of sort memory; increase server sort buffer size


Go to End


9 Posts   29993 Views

Avatar
Willr

Forum Moderator, 5523 Posts

3 December 2010 at 11:13pm

DataObject:get doesn't seem to well thought through and optimised.

DNA to answer your question DataObject::get is not (very) optimized and it does comes with the associated performance implications (try doing a DataObject::get('Page') on a ~20,000 page site!). You should use SS_Cache to cache any large sets from the front end if you want to keep tabs on performance.

Planning has been underway for how to replace the current accessing structure (http://open.silverstripe.org/wiki/development/NewDataMapper) Sam has already tried his hand at initial versions of the new functionality so it'll hopefully make its way into SilverStripe 3.0! Keep watching this space.

Another area a couple devs are investigating is how to reduce the number of queries SS makes. When you save a page in some parts of the CMS it can make a crazy amount of queries (one dev had ~700 per site publish) so its one area where the framework could use a bit of a cleanup.

Go to Top