As we approach an Elgg 1.1 release tentatively set for next week, the core developers have been focusing on database performance. Many earlier adopters have complained about Elgg’s performance.
Today alone, Marcus Povey tweeted that he removed over forty database queries and reported that Elgg is noticeably faster since those changes. Marcus also reported some other things that he was working on.
One item is a Garbage Collector.
This garbage collector removes clutter from Elgg’s mySQL database by eliminating data no longer needed in the elggmetastrings table. As you can see from the image above, administrators have the option of collecting “garbage” once per week, month, or year.
Another new administrative feature in this area is the log rotator. Anybody who has perused Elgg logs knows how astonishingly fast Elgg’s log amasses entries. This feature is similar to the garbage collector in that it clears out data at intervals set by the administrator.
Instead of deleting the data, it archives it, leaving you access to the data, but reducing the overhead on the database.
It’s great to hear that the Elgg team has responded to concerns about its performance. I cannot verify the differences these make to Elgg’s performance. I’d love to hear from others who can test these claims.
Again, these changes are available only in the trunk SVN. The trunk is relatively untested and should not be used on a production site unless you are able to restore your site with backups.
Loading ...
Recent Comments