I have two observations:

1. The performance comparison tests should be conducted on larger # of nested page nodes. Currently, I only see it’s done on 1800 pages. We’ve seen the performance bottleneck gotten worse when there are 5000 – 10,000 pages.

In the case of 5000 pages, I did one test, and it revealed that the bottleneck was actually not the algorithm itself – it’s because the old algorithm returns ALL pages, and for every page, we did expensive update_post_caches(), and apply_filters(‘the_posts’, $this->posts).
Ex: for total of about 60 seconds – 17 seconds are spent in update_post_caches(), and 11 seconds are spent in apply_filters(‘the_posts’, $this->posts)

With MPTT, the # of returned pages will be much smaller, so conceivably, the saving would be great. It would be nice to identify those bottlenecks, and make sure the new MPTT addresses those bottlenecks.

2. I did a little bit more optimization on existing algorithm.
http://core.trac.wordpress.org/ticket/10852 and http://core.trac.wordpress.org/ticket/10853.
It’d be interesting to compare the performance again with those two changes.

Hello everyone, since my last update I fixed some bugs about upgrade and some strings for update the mysql.

Finally, I can say that the speedup wasn’t much superior, maybe get the lft and rgt values in the sql queries add more time in the process. But I have a good news, the speedup in Edit Pages section in admin panel have a good acceleration, see the chart: http://spreadsheets.google.com/pub?key=tvUiOf6bEO5A55cMLjbDTdw&output=html

The last patch is in http://dl.getdropbox.com/u/173207/diff-20090817.patch . Remember, only apply the patch on a test WordPress installation.

Thanks to all, these months were really good .

Final evaluations begin today. I know some of you are continuing to work on your projects, but your grade for Google’s sake will be based on what you have as of today. Thank you all for your hard work! It’s been great having you work with us, and we hope you will continue to be involved in the WordPress community. Please be sure to fill in your evaluations for your mentors and the organization (WordPress) when you get the notice from GSoC that they are available. I’ll be following up with each of you individually to get some additional feedback from you about what we can do better to support students next year, as well as to put together a presentation on your GSoC projects that we will publish online.

Feel free to continue using this blog on any projects you are continuing work on, as we’ll leave it open.

Thanks again, and good luck to all of you from all of us!

Hello Everyone Sorry for the extreml…

Hello Everyone

Sorry  for the extremely late update. As I let Andy know, I was on vacation this week.  My parents got a cottage up in West Virginia and I was invited to come stay with them Monday-Friday. I was also in and out of service so I was unable to post my update on Wednesday.

I actually meant http://gsoc2009wp.wordpress.com/2009/08/08/220/ to be an early status update so that information applys here.

The demo is also running the latest version and the latest version is available in the plugin repository.

All that is left now is a final look over for me. It’s the last few days so good luck to everyone else!

Looks like I am the last. Sorry for the delay, but I am not settling for releasing sub-par work. This new patch is of course subject to bug hunting and further refinement between now and the GSoC deadline. I am still working on the documentation. Please patch it on a new rev. 11804 trunk, as it relies on the installation process to initialize some variables.
I have changed the implementation of albums from using a new post_type to using taxonomies.
Feature overview: you can add / edit / trash photos, add / edit / delete albums, make one album a child of another. Use /photo/ and /album/ permalinks to access the photos, e.g. /photo/ for photostream, /photo/16 for photo with ID 16; /album/gsoc-2009/meetings for the meetings album under gsoc 2009 album.
Enjoy:

• Photopress Patch 12th Aug 2009
• Photopress Demo usr:admin / pw: gsoc2009

Please do tell me if there are bugs. I will fix them ASAP. Thanks.

Sorry for delaying my report by a day. I felt it worth it, as I was finishing up on what should hopefully my final patch for the GSoC term (subject to review by other developers and subsequent editing of course) and some performance results.

• MPTT Patch 08/12/2009
• MPTT Performance Comparison

The patch applies to rev. 11807. Please feel free to test it out and report any issues you experience. Just don’t trust important data to it yet.

Beau did a demo of Elastic last night at the SF WordPress Meetup, and it was awesome. Daryl, very impressive. Looking forward to seeing the continued evolution of this project.

Hey,

You can check out Buildpress demo here at http://demo.webdevcodex.com
You can test buildpress by logging on to the admin side http://demo.webdevcodex.com/wp-admin
(user : test, pass : test)

You can download it from
http://buildpress.googlecode.com/files/buildpress0.3.0.rar (just extract it to your wp-content/themes) directory
Activate theme Buildpress from Appearancefrom your WordPress Admin. (you`ll notice a subpage Buildpress in “Appearance”)

Regards

Hi everyone, finally I have the patch for MPTT in categories and Pages.

Download the update-pack in http://dl.getdropbox.com/u/173207/pack_20090810.tar.gz

The update-pack includes the patch for WordPress (developer version at today), and two plugins called MPTT, and MPTT-test.

The first plugin MPTT, include a little code for view the tree data in categories and pages (only for view and check the results of add/edit nodes). And with the second plugin MPTT-test, you can insert artificial tree data (hundred and thousands nodes) into categories and get the speedup MPTT V/S Recursive way for get categories.

Remember install the diff patch only in a not important WordPress installation.

Bye bye, and good luck with the tests!

Elastic 0.0.2.1

Hey everyone. The past week has seen quite a few improvements to both the framework and the editor. Both are now relatively stable and working together, which is pretty exciting. A big thanks to everyone who tuned in to the dev chat—it was great to talk to you guys and answer your questions.

elastic-0.0.2.1 can be downloaded here: http://code.google.com/p/elastictheme/downloads/list
For those of you that downloaded the editor during the dev chat, this should fix the issue in 0.0.2 where the UI wouldn’t load properly.

I’m going to try and pack in a bunch of new features/improvements before Monday, which is where you guys come in. Let me know what you’d like to see! I’d love to know what you feel would make Elastic most effective.

Here are some of the features I’m planning on adding. All of them probably won’t make it into the editor by Monday, but hopefully a few will.

[Editor] Typography: Let the user select fonts for the headers and body. This is in progress.

[Editor] Backgrounds: Let the user select background colors (for the body and modules). Background images will eventually be supported (with potential integration with the media uploader), but not by Monday.

[Editor] Fix Whitespace Rendering: Currently, the editor does not render whitespace between modules correctly. Whitespace will basically serve as the editor’s implementation of margins. This is not a simple addition, and will come with a slew of other improvements.

[Framework] Customized Headers: The headers in the framework are very sparse. This will improve by Monday.

[Framework] Better Defaults: Most of the framework’s default views (html and css) are derived from Ian Stewart’s Shape theme (Thematic’s leaner cousin). I’d like to have some more customized defaults, but now may not be the time.

It’s crunch time! Good luck everyone.