A new version of the eccomerce platform, Magento, was released on these last days of March. New features and improvements included in Magento 1.3 since the release of version 1.2 include:
Added support for customer file upload and date/time/datetime custom options
Described all methods in WSDL for SOAP web-services to improve compatibility with .NET, Java and other languages
Frontend Flat Catalog and improved performance. From early test and benchmarks the developers are seeing up to a 40% performance improvement when comparing to Magento 1.2.x both in page loads and memory usage.
That 40% improvement is substantial and the Magento folks are promising the release of more formal resting results soon.
2bits.com: "The intranet used a lot of [Drupal] contributed modules, with 35 custom developed modules for this application. It would serve a user base of more than 80,000 employees. Testing of the application showed that only 30 concurrent users can be active simultaneously, falling well short of the requirement for 200 users to be active at any given time...
...We quickly found that we could not go beyond around 50 users, and starting diagnosing the problems with the application that prevents it from scaling. Here are the findings, and the solutions..."
Alldrupalthemes.com did a performance comparision between Joomla 1.5 & Drupal 6.1. As the author of the post infers, the numbers collected may not mean much to the user in the "real world" and limitations in the test results should be noted. Nevertheless, numbers that compare Drupal and Joomla performance are always interesting.
The conclusions drawn from the results are:
Drupal is significantly faster than Joomla in all 4 setups
Drupal cuts down pageload time by ~74% when caching is enabled on the fresh install and ~86% with the more populated setup
Joomla cuts down pageload time by ~23% on the fresh install and ~20% on the more populated setup
These numbers are interesting and I bet the study pulls in a lot of visitors for All Drupal Themes. Not only are Drupal and Joomla users interested in these type of posts, but so are potential users shopping around the first time for a CMS. As always, you should judge a CMS by what it does for you and not what it does for others.
"Check your Plone site's cachefu setup: small improvements
can help a lot. I assume you've got a basic cachefu setup pat down already,
which only means adding your few custom content types to the "content" or
"container" rules and saying you've got squid (and/or apache) in front. You
get good results with that: this blog entry helps you pinpoint some extra
improvements."
A few days ago, I mentioned that "Drupal 6 feels ready to me" for public release. Evidently, that was more than feeling as Drupal 6 was released early Wednesday morning.
As a user of Drupal, let me start by saying thank you to
all the developers and advocates that brought Drupal 6 to light. I've
been watching Drupal 6 grow from a distance this past year and have made some observations. There is a lot more sweat, tears, and love put into Drupal than most outsiders realize. Those of us that have used Drupal during the past six years owe a lot to those of you active in the Drupal community.
You can check out the release announcement
at Drupal.org for all the new features and enhancements that have been
rolled into Drupal 6. Let's look at some of the highlighted features in
Drupal 6 which I've listed below.
"DotNetNuke 4.4 introduced a number of performance enhancements. Many of these enhancements required the creation of new overloads of some common methods and deprecation of the existing methods.
It is important for module developers, who wish their modules to take advantage of the new performance features to update their modules for performance."