Fix the "Current Activity" link. #224
Comments
|
Did some research. When running in development, this returns (using a copy of a production database). Not extremely fast, but it is returning a page. There doesn't look to be anything too egregious in the sql query. Then, when updating the log level in production so I can see what queries are happening and which one is taking so long, it started returning results there too. This needs more looking into, but it's looking less like a software problem and more like a server problem. |
|
Adding an index did improve the slowest query in development by a factor of 1000, so that hopefully that will be enough to make production snappy. Will need to take a look when this fix makes its way there. |
The Current Activity link was slow and in production the versions lookup was taking 5-40 seconds. In development, it was taking 1.5 seconds, and this index improved that to 1.5 milliseconds. Issue #224: Fix the "Current Activity" link.
Fix #224: Add an index to versions
|
OK, thanks @frankduncan. I'm still not quite sure how the Current Activity feature will get used operationally but I sense it will be really useful for DAT Managers who want to see what's going on without having to open individual incident reports. |
Wish I had the full URL to that link -- @OhMcGoo has it, though. I think it's different from "Currently Open Incidents" (
incidents/CHAPTER_SHORTNAME/incident/activity).There's such a long wait time right now that apparently even Jim has never seen the inside of this chamber in the temple.
The text was updated successfully, but these errors were encountered: