Noticed a query on the node table in a case where in 99% of cases the node will already be cached in memory. If we're viewing comments, we're almost always viewing their parent node too. If we're not viewing the parent node, then it's on pages like comment/n/reply where performance is less of an issue than node/n anyway.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | comment_mode_queries.patch | 777 bytes | catch |
| comment_mode.patch | 1.39 KB | catch |
Comments
catch’s picture
| Status | File | Size |
|---|---|---|
| new | comment_mode_queries.patch | 777 bytes |
re-roll since re-test reports seem to be stuck and this one doesn't have 30 lines of cvs crud at the top of it.
dries’s picture
Comment #4
dries commented Status: Needs review » Fixed
Good catch! Committed to CVS HEAD.
Status: Fixed » Closed (fixed)
Automatically closed -- issue fixed for two weeks with no activity.
Comment #1
The last submitted patch failed testing.