In the 4.6 model -- even with the backport url_alias patch -- I altered drupal_lookup_path() to disallow any lookups that didn't come from path aliases.<br><br>Since I set the rules for that site, it meant paths were only checked if:
<br><br>1) $path == 'taxonomy/%'<br>2) $_GET['q'] == $path<br><br>This prevented the menu, node links, comment links, et. al. from being processed. It cut path lookups from 200+ to under 10 for node page views.<br><br>Now this isn't a universal solution, but it may suggest a plan.
<br><br>- Ken Rickard<br>agentrickard<br><br>>>> Maybe we should run the modified devel.module on <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://drupal.org/" target="_self">drupal.org</a> to
<br>>>> see what the most expensive queries are?<br>>><br>>> SELECT * FROM url_alias, I'd be surprized if that had changed. The<br>>> individual query is very short but there are probably 120 per page
<br>>> on average.<br>><br>> Are there reasonable assumptions we can make about certain URLs?<br>> Like, can we assume that people don't want to alias '?q=qcomment/<br>> reply/123'? Or ?q=contact? Or q=user/register and ?q=user/
<br>> password? If we can make some simple assumptions, we might be able<br>> to save a helluvalot database queries (per page view) ... Food for<br>> thought.<br><br>Any thoughts here?<br><br>