Actions
Architecture #1408
closed
Add optimisations in the reports system
Status:
Rejected
Priority:
5 (lowest)
Assignee:
Category:
Web - Compliance & node report
Target version:
Pull Request:
Effort required:
Name check:
Fix check:
Regression:
Description
We should create a VIEW containing the last execution time per node, and use it in the immediate reports
The for yield are probably not top optimised (a lot of identical filters) in th ExecutionBatch
Updated by Jonathan CLARKE over 13 years ago
- Target version changed from 15 to 16
Updated by Jonathan CLARKE over 13 years ago
- Target version changed from 16 to 10
Updated by Jonathan CLARKE about 13 years ago
- Target version changed from 10 to 18
Updated by Jonathan CLARKE about 13 years ago
- Target version changed from 18 to 24
Updated by Jonathan CLARKE over 12 years ago
- Target version changed from 24 to 18
Updated by Jonathan CLARKE over 12 years ago
- Target version changed from 18 to Ideas (not version specific)
Updated by François ARMAND almost 12 years ago
- Tracker changed from User story to Architecture
- Status changed from New to Discussion
Is this still relevant with the work on real-time reporting done ine 2.4/2.5 ?
Updated by Nicolas CHARLES almost 12 years ago
Yeah, there are still unefficient part; but it won't be improved before 2.6 for sure
Updated by Nicolas CHARLES over 11 years ago
- Status changed from Discussion to Rejected
This make no sense now; especially this the view is not really optimized, and it wouldn't improve perfs.
I'm rejecting this
Actions