<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">We did do an EXPLAIN ANALYZE on every query in our installation (by exposing each one with devel) and this included a large number of contributed modules. The most problematic queries were the ones coming from user_points and views, which should come as no surprise, </blockquote>
<div><br>A patch by a large site was commited. It adds a few indexes that increase the performance for the txn table.<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The most significant problem we faced, outside of straight up bad queries, was repetitive queries. The userpoints module was challenging to work with and we did need to rewrite most of the data access there to make it suitable for a production environment. There are other modules we changed, but this one required the most effort. We had some pages that were hitting the points tables over 100 times per page load, even for anonymous users with memcache installed.<br>
</blockquote><div><br>If this is a list of users with points for each listed beside their names, then yes, it has to query the table several times on the page. Just like user_load or node_load for different users/nodes.<br>
<br>If you have implemented some sort of smart caching, then we are looking forward to your patches in the issue queue.<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
What's ironic about this discussion is the PostGres developer base is growing at a faster rate than MySQL and adoption is increasing for a number of other FOSS projects. </blockquote><div><br>What I have seen is that Sun's purchase of MySQL, and MySQL's management revoking the open source aspect of some features, then reversing that decision, all this has not gone well with some.<br>
<br>Moreover, the departure from MySQL/Sun of Jim Starkey, architect of the new transactional Falcon engine, and Oracle's ownership of InnoBase has left the question of the future of a transactional engine (Maria is not transactional, just a replacement for MyISAM). PostgreSQL has been transactional from the start though.<br>
</div></div>-- <br>Khalid M. Baheyeldin<br><a href="http://2bits.com">2bits.com</a>, Inc.<br><a href="http://2bits.com">http://2bits.com</a><br>Drupal optimization, development, customization and consulting.