| Project: | Project issue tracking |
| Version: | 6.x-1.x-dev |
| Component: | Issues |
| Category: | task |
| Priority: | normal |
| Assigned: | bdragon |
| Status: | needs work |
Issue Summary
This started out with me poking at one of the blocks earlier after someone complained that the updated marker wasn't working properly. Then I found out killes had turned on caching.
After experimenting for the better part of the day, I determined that the best way to improve performance would be to keep a timestamp in {project_issues} and using that to sort chronologically instead of {node_comment_statistics}. This seems to eliminate all of the temp table crap that's happening in the issue views completely.
I will be hopefully testing this on scratch tomorrow, schedule permitting.
Known issues:
* The timestamp doesn't update if you go and edit the node by hand.
-- Mainly because I couldn't find an existing place to hook in. Does nothing at all in project_issue care about issue nodes being edited manually?
| Attachment | Size |
|---|---|
| project_issue_fast_sorting.patch | 25.78 KB |
Comments
#1
Setting back to needs work. There are some other pieces that are affecting view performance and preventing this from working fully.
Still looking at it.
#2
Rerolled, we are having performance issues again.