From: <b class="gmail_sendername">Massimo Di Pierro</b> <span dir="ltr"><<a href="mailto:massimo.dipierro@gmail.com" target="_blank">massimo.dipierro@gmail.com</a>></span> <br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="gmail_quote"><div style="word-wrap: break-word;"><div>For a typical web app my experience is the bottle neck is the database and independent on the framework.</div>
</div></div></blockquote><div><br>Having been a relatively advanced user of Drupal, to me the direct cause of slowdown was the framework itself. Not in the time it took to execute the lines of code but because of the SQL requests and datastructures underlying the framework (node ids, revision ids, permissions, views, etc... would generate a lot of requests to view a simple page). So I generally wouldn't consider the database speed independent of the framework as long as the framework does some automatic database request generation and type handling. This became particularly obvious as the database grew bigger and the framework became slower.<br>
</div></div><br>That being said, this could be a Drupal specific issue and may be web2py database is better optimized (e.g. closer to human written data-structures and requests).<br>