We updated the Module Development Guide to reflect the latest Cuyahoga version. Get it here!

One of the things that is still on our list is updating the module development guide to reflect the current Cuyahoga version. In the meantime, Paolo Corti has published a nice tutorial about creating a simple Hello World module for Cuyahoga 1.5. You can find it here: http://www.paolocorti.net/public/wordpress/index.php/2007/04/30/cuyahoga-hello-world-sample-module-tutorial/.
Thanks a lot Paolo!

We just started the CuyahogaContrib project on SourceForge. This project is especially for Cuyahoga related projects that are not part of the core project.

It's very easy to join this project: if you have a module or other add-on that you want to share with the community, you're invited. Just drop an e-mail at martijn [at] boland *dot* org with the project description and a little motivation.

A few simple rules:

• Each developer is responsible for their own sources;
• Developers must make sure that the source is compatible with the current Cuyahoga SVN trunk;
• Developers can pick their own license for the contributions as long as the license isn't too restrictive (so no GPL, sorry guys);
• When using databases: please try to support all three supported platforms (SQL Server, MySQL and PostgreSQL);
• Any contribution is welcome as long as it is useful. It doesn't need to be rocket science :).

The Flash module and the Forum module have already been moved to this project so the contributors can maintain their sources more easily.

You can find the project at http://sourceforge.net/projects/cuyahogacontrib and the SVN root folder is at https://cuyahogacontrib.svn.sourceforge.net/svnroot/cuyahogacontrib.

Finally!

About a year ago we started thinking about the Cuyahoga 2.0 version. All great ideas: we'd have a new admin UI, the concept of content abstraction was introduced and many many more things. For different reasons development went not so quickly as expected, but there still was progress. One of the first things that were done was rebuilding the underlying architecture by using the Castle IoC container to make Cuyahoga much more extendable en flexible.
In the meantime when development crawled forward, people already started using the development version, mainly because it was targeting .NET 2.0. To support these people, we decided to create an intermediate release that includes the new foundation, new modules and lots of minor improvements and bug fixes.
Unfortunately there still isn't a new administration UI, but it is scheduled for the next major release.

Highlights:
- new foundation;
- new Flash module (contributed by Gabe Varela, Xylem Interactive);
- new Forum module (contributed by Patrick Gahan, originally created by Steen Rabol;
- new Sitemap module;
- XHTML compliant output;
- improved Articles module with paging and archive;
- improved performance.

You can download the new release from the Sourceforge site:

• Source package

• Binary package

• Release notes

Existing users: check the upgrade instructions! Also, the installation instructions can be found here for the binary version and here for the source version.

Thanks to everyone who helped by submitting bugs and contributing patches, ideas, etc.!

In the past different people have asked information about how many users Cuyahoga can handle. Finally we have some information about this subject that might be useful.

For the 1.5.0 release we have done some performance tests to verify that the new architecture with Castle performs just as good as the 1.0.x release and to make sure there are no memory leaks.

All tests were performed with Microsoft Application Center Test and the server was a dual core Pentium D 2.8 Ghz with 2 GB RAM with Windows 2003 Server, IIS 6 and SQL Server Express 2005. The test site was a copy of this very site, (25 pages (forum excluded) and 800 registered users). For most sections, output cache is set to 60 seconds and the second level cache is set to 30 seconds.

So here are the results:

Cuyahoga 1.0.1
About 230-260 requests per second with 95% CPU load. This includes static content, but most requests were aspx pages.
Memory usage for the w3wp.exe process was stable at 50MB.

Cuyahoga 1.5.0
About 280-400 requests per second with 90% CPU load.
Memory usage for the w3wp.exe process was stable 61 MB.

Remarks:
- During the tests, there was almost no load on the database.
- The differences in requests per second for 1.5.0 were caused by modules that leverage Castle's automatic transaction management (Articles and Downloads). Creating one of these modules almost doubled the page execution time.
- We did have a memory leak in the 1.5.0 version. This was because we registered all aspx pages in the Castle container and it seemed that those pages were not released properly. After removing registering the aspx pages in the container, memory usage was stable.

In conclusion we can say that Cuyahoga 1.5.0 now performs at least as good as Cuyahoga 1.0.x. Implementing the Castle container in a sensible manner didn't hurt the performance. All credits to the Castle guys for building these brilliant tools!