-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Platform: All, OS: Linux
Some of my projects are very big, when I click on a crap4j report icon to open
report it takes a very long time for the report to load.
If I click on another link (example build history) and then click the browser
back button, the page takes a very long time to re-load.
[JENKINS-4480] It takes a very long time for the report to load.
eagleigor
added a comment - Hi,
It take more than two minutes to open report page.
Here is info from crap.xml file:
<name>Method Crap Stats</name>
<totalCrap>478206.0</totalCrap>
<methodCount>29282</methodCount>
<crapMethodCount>2313</crapMethodCount>
<crapMethodPercent>7.9</crapMethodPercent>
<crapLoad>22713</crapLoad>
Unfortunately I can not send to you report.xml file, but file is big - 18.1 MB
(19,025,072 bytes)
eagleigor
added a comment - Hi,
It take more than two minutes to open report page.
Here is info from crap.xml file:
<name>Method Crap Stats</name>
<totalCrap>478206.0</totalCrap>
<methodCount>29282</methodCount>
<crapMethodCount>2313</crapMethodCount>
<crapMethodPercent>7.9</crapMethodPercent>
<crapLoad>22713</crapLoad>
Unfortunately I can not send to you report.xml file, but file is big - 18.1 MB
(19,025,072 bytes) 
miq
added a comment - I have the same problem. I will try to quantify my experience and upload the file if it is not to large.
miq
added a comment - I have the same problem. I will try to quantify my experience and upload the file if it is not to large. miq
added a comment - crap.xml size ~ 5MB
Load time main chart ~ 45s
Load time crap report ~ 2:50m
Info:
<name>Method Crap Stats</name>
<totalCrap>273956.22</totalCrap>
<crap>33.01</crap>
<median>2.00</median>
<average>33.01</average>
<stdDev>327.11</stdDev>
<methodCount>8299</methodCount>
<crapMethodCount>695</crapMethodCount>
<crapMethodPercent>8.37</crapMethodPercent>
<crapLoad>9280</crapLoad>
miq
added a comment - crap.xml size ~ 5MB
Load time main chart ~ 45s
Load time crap report ~ 2:50m
Info:
<name>Method Crap Stats</name>
<totalCrap>273956.22</totalCrap>
<crap>33.01</crap>
<median>2.00</median>
<average>33.01</average>
<stdDev>327.11</stdDev>
<methodCount>8299</methodCount>
<crapMethodCount>695</crapMethodCount>
<crapMethodPercent>8.37</crapMethodPercent>
<crapLoad>9280</crapLoad> 
Thank you for this problem report!
The load time for a crap4j report is directly related to the amount of "crappy"
methods. Can you try to quantify your delays? How long does it take to load the
report? How many classes are part of the project and how many crappy methods are
reported?
These numbers help me get a feeling of what goes wrong. If your project
guidelines permits it, you can even upload a big report.xml obtained from
crap4j. I would then be able to reproduce your problem on my machine.