Project

General

Profile

Actions

Architecture #1408

closed

Add optimisations in the reports system

Added by Nicolas CHARLES over 12 years ago. Updated over 10 years ago.

Status:
Rejected
Priority:
5
Category:
Web - Compliance & node report
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

Actions #1

Updated by Jonathan CLARKE over 12 years ago

  • Target version changed from 15 to 16
Actions #2

Updated by Jonathan CLARKE over 12 years ago

  • Target version changed from 16 to 10
Actions #3

Updated by Jonathan CLARKE over 12 years ago

  • Target version changed from 10 to 18
Actions #4

Updated by Jonathan CLARKE over 12 years ago

  • Target version changed from 18 to 24
Actions #5

Updated by Jonathan CLARKE over 11 years ago

  • Target version changed from 24 to 18
Actions #6

Updated by Jonathan CLARKE over 11 years ago

  • Target version changed from 18 to Ideas (not version specific)
Actions #7

Updated by François ARMAND about 11 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 ?

Actions #8

Updated by Nicolas CHARLES about 11 years ago

Yeah, there are still unefficient part; but it won't be improved before 2.6 for sure

Actions #9

Updated by Nicolas CHARLES over 10 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

Also available in: Atom PDF