Please enable JavaScript.
Coggle requires JavaScript to display documents.
Analyzer Code Diagnosis Inception, Estimation Criterias, Estimation,…
Analyzer Code Diagnosis Inception
load and display CS
Local CS
1d
DB Stored CS
1d
Average Actual Performance: 49 sec
Note: this value was calculated by me, and it represents the Average time of all users input data
Expected Perrformance: 5sec
export CS to DB
Monte Carlo
2d
N/A
N/A
TOX
901 sec
11 sec
1.5d
Manually created 3DCS
1d
save and share CS in DB
Save TOX
97
11 sec
2d
Save Monte Carlo
21 sec
315
2d
folder tree refresh
N/A
N/A
Pending
global strategy for Analyser perfo improvement
Outside the coding part
As most of the points where we're having perfomance issues come from parts where there's need to access the database. And this issue reduce porfmance even more when Nomad is being used
Nomad Issue => Cannot be tackeled
load analyser
N/A
N/A
Tree Loading
Pending: 3d
Local and saved CS Loading
Some improvements not specifically related to mentioned functions could bring benefits for the overall module
Import TOX
After discussion with Sylvain
Import Monte Carlo
Estimation Criterias
Dividing each point into sub points
Coding part
Comparing current and expected performance time
SQL Part
Debugging part
Expected performance cannot necessary be reached
Estimation
Think about a way to split
Split by Action
Split by type of activities
Split by document part
code flow
potential performance gain
implementation time
Document Estimation
Regular meetings with Julien to be estimated
Create US for improvements => time needed fto implement technical modification
Result Document
code flow with timing
potential performance gain for each proposed modification
Implementation Time