<html><body><div style="color:#000; background-color:#fff; font-family:arial, helvetica, sans-serif;font-size:12pt"><div><span>Thanks, Jamie and Earnie. I finally found the code in a block. The queries had an incredibly bad sub-query for an IN clause. But it turns out that the block was a first attempt to get the data that the Views were generating, so the block wasn't even needed anymore. Removing that block brought the page down to 1.5 seconds. 10 hours to find, 10 seconds to fix...<br></span></div><div> </div><div><font color="#ff007f" face="bookman old style, new york, times, serif" size="4"><font style="color:rgb(0, 0, 0);" size="2"><span style="font-family:arial, helvetica, sans-serif;"></span></font></font><font color="#ff007f" face="bookman old style, new york, times, serif" size="4"><i><b>Nancy</b></i></font> <br></div><div><font face="arial, helvetica, sans-serif">Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King,
Jr.</font></div><div><br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; margin-top: 5px; padding-left: 5px;"> <div style="font-family: arial, helvetica, sans-serif; font-size: 12pt;"> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div dir="ltr"> <font face="Arial" size="2"> <hr size="1"> <b><span style="font-weight:bold;">From:</span></b> Jamie Holly</font><br></div>
What Earnie said. Whenever you do sites with views, it's always best to <br>spend some time and put the queries into mysql and do an explain. Even <br>if you see queries executing in decent times, it's still best to double <br>check because it could still be doing a full scan, but you just don't <br>have that much data in at development.<br><br>A lot of times you can fix them with indexing, but there are the <br>occasions when you actually need to rewrite the query in a module.<br> </div> </div> </blockquote></div> </div></body></html>