login->tickets->reports->hit plus sign->reports take longer to load. I timed it where it was taking me 27-50 seconds on the initial load. Customer is reporting it takes field users up to 5 minutes to load.
Then do that
Followed by this
Expected Result
faster load time
Actual Result
slower load time up to 5 minutes per customers field users
Analysis
Wassim [2:07 PM]
I am able to replicate victor’s issue on report performance v3 vs v4. this happens when you login ->tickets->reports-> click plus sign and on that initial request its took me 27-50 seconds to load but after that its fine. When i went to biweekly with the same steps it took 2 seconds.
dpitre [2:20 PM]
:disappointed: i don’t think that can be helped
the reason why is that the pdf processor is loaded in the same library as the html processor
the pdf processor is massive…. the whole device slows down while it’s loading it
that’s why it only affects the device on the first run
3353 doesn’t even have pdf support
Wassim [2:22 PM]
he’s all on html
dpitre [2:22 PM]
yep
take it up with tom, if he decides we should work on it i may be able to split it back out for optimization
Wassim [2:23 PM]
so on biweekly there isn’t pdf so it loads faster, on v4 the pdf process as you said its in the same library so it lags
gotcha
dpitre [2:23 PM]
yep on the initial load it will do that
Wassim [2:23 PM]
great, at least i understand why its happening. Victor was thinking has to do something with sharing
dpitre [2:23 PM]
maybe we can more agressively load it but that would just cause the app to hang in a different spot
no….not at all, it’s just because of that massive pdf library
did you create a card for it?
i would create a card and write all of this down, you can even copy paste this conversation :wink:
and then i would show it to Tom
you did good work by noticing it
Wassim [2:36 PM]
i haven’t - i was just able to replicate it today on a go tomeeting with victor as i couldn’t see it before
dpitre [2:37 PM]
yeah…. but now that you know what it is, it takes nothing to reproduce
that’s just the way the app works
Mingle Card: 6231 Steps to Reproduce
Expected Result
faster load time
Actual Result
slower load time up to 5 minutes per customers field users
Analysis
Wassim [2:07 PM]
I am able to replicate victor’s issue on report performance v3 vs v4. this happens when you login ->tickets->reports-> click plus sign and on that initial request its took me 27-50 seconds to load but after that its fine. When i went to biweekly with the same steps it took 2 seconds.
dpitre [2:20 PM]
:disappointed: i don’t think that can be helped
the reason why is that the pdf processor is loaded in the same library as the html processor
the pdf processor is massive…. the whole device slows down while it’s loading it
that’s why it only affects the device on the first run
3353 doesn’t even have pdf support
Wassim [2:22 PM]
he’s all on html
dpitre [2:22 PM]
yep
take it up with tom, if he decides we should work on it i may be able to split it back out for optimization
Wassim [2:23 PM]
so on biweekly there isn’t pdf so it loads faster, on v4 the pdf process as you said its in the same library so it lags
gotcha
dpitre [2:23 PM]
yep on the initial load it will do that
Wassim [2:23 PM]
great, at least i understand why its happening. Victor was thinking has to do something with sharing
dpitre [2:23 PM]
maybe we can more agressively load it but that would just cause the app to hang in a different spot
no….not at all, it’s just because of that massive pdf library
did you create a card for it?
i would create a card and write all of this down, you can even copy paste this conversation :wink:
and then i would show it to Tom
you did good work by noticing it
Wassim [2:36 PM]
i haven’t - i was just able to replicate it today on a go tomeeting with victor as i couldn’t see it before
dpitre [2:37 PM]
yeah…. but now that you know what it is, it takes nothing to reproduce
that’s just the way the app works
Related Cards
Impact Analysis
Developers: Fill in this area during code review.
Test Plan