StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Yes. I can confirm. However.</p> <p>First the bad news:</p> <ul> <li>Drupal7 core is more complex. Complexity costs performance. </li> <li>Drupal7 core is bigger: more features, more in core. <strong>more</strong> equals <strong>slower</strong>. </li> </ul> <p>Then the theory:</p> <ul> <li>In Drupal6, approx. 95% of the projects included CCK. Call that Drupal+. Drupal7 comes with CCK out of the box. Drupal6+ is <strong>slower</strong> then Drupal7. </li> <li>Drupal7 offers a lot of enterpris-ish abilities for performance tuning. Memcached, (Varnished)Proxy support, Database balancing (master/slave etc). Something that Drupal6 could not do. </li> </ul> <p>However, <a href="http://groups.drupal.org/node/142529" rel="noreferrer">Drupal6 pressflow had these enterprise-ish things build</a> in (in fact: these pressflow features made it into core, offering the basis for Drupal7). </p> <p><a href="http://2bits.com/articles/performance-benchmarking-drupal-512-drupal-66-and-drupal-7x-we-are-getting-slower.html" rel="noreferrer">Drupal7 is slower then Pressflow Drupal6</a>. Drupal7 offers performance features that Drupal6 did not offer, but that PressflowDrupal6 did offer.</p> <p>Many projects also have views module enabled. Views3 in Drupal7 offer a lot of performance improvements (enterprise-ish features) over Views2 for Drupal6. </p> <p>My advice: untill there is a performance-optimised Drupal7 (Pressflow Drupal7, for example) Just stay with your Pressflow Drupal 6. It is in both theory and practice a lot faster. If you can benefit from the Views3 improvements and features, then go for Drupal7+views3, that will give you more options to tune performanceissues.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload