MantisBT - CDash
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0006515CDashpublic2008-03-05 20:532008-07-30 10:03
ReporterBill Lorensen 
Assigned ToJulien Jomier 
PrioritynormalSeveritymajorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version1.0 
Summary0006515: Performance issue with "Nightly Changes"
DescriptionClicking nightly changes can take from 2 to 6 minutes. At least for itk and cmake.
Steps To Reproducehttp://public.kitware.com/CDash/viewChanges.php?project=Insight&date=20080305 [^]

http://public.kitware.com/CDash/viewChanges.php?project=CMake&date=20080305 [^]
Additional InformationAs suggested befroe, I think a static page should be generated. The nightly changes do not change for a given dashboard and can be generated once.
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2008-03-05 20:53Bill LorensenNew Issue
2008-03-05 21:18Bill HoffmanNote Added: 0010719
2008-03-05 21:18Bill HoffmanStatusnew => assigned
2008-03-05 21:18Bill HoffmanAssigned To => David Cole
2008-03-05 22:49Julien JomierNote Added: 0010720
2008-03-05 22:55David ColeNote Added: 0010721
2008-03-05 23:00Bill HoffmanNote Added: 0010722
2008-03-05 23:03Julien JomierNote Added: 0010723
2008-03-05 23:03Julien JomierAssigned ToDavid Cole => Julien Jomier
2008-07-30 10:03Julien JomierStatusassigned => closed
2008-07-30 10:03Julien JomierNote Added: 0012877
2008-07-30 10:03Julien JomierResolutionopen => fixed
2008-07-30 10:03Julien JomierFixed in Version => 1.0

Notes
(0010719)
Bill Hoffman   
2008-03-05 21:18   
Dave, I think we might have to go to a client or cron based approach to this one. If we can have one of the nightly clients send in the nightly change information that would be good. Anyway, it needs to be fixed.
(0010720)
Julien Jomier   
2008-03-05 22:49   
I think I know how to solve this. I need to test it but the idea is to run an ajax request on the first build submitted to the dashboard, we then store the result in the database. The only issue will be if we change the nightly start time, the previous days won't be really shown correctly, but I think it's not a big issue.
(0010721)
David Cole   
2008-03-05 22:55   
No. The nightly updates submitted by the machines that run nightlys do not contain all the changes shown by the nightly changes page.

The nightly changes page shows all revisions of the files changed in the 24-hour period. It also shows activity on branches. It is entirely *not* the same as any of the nightly submissions in many cases.

The nightly submission from a given machine may contain many days worth of changes (if it hasn't run for many days) which would be inappropriate to represent as "the nightly changes" for a project.

It would be right *most* of the time, but I think I should work on getting this cvs rlog output cached into the database and then be able to do a simple query on the db to implement the nightly changes page...
(0010722)
Bill Hoffman   
2008-03-05 23:00   
OK, so I am not sure what an ajax request is... Sounds like we need to run cvs rlog once a day shortly after the nightly start time, and store the results in the database. Can the ajax request do that?
(0010723)
Julien Jomier   
2008-03-05 23:03   
Sorry my previous message wasn't clear. The ajax request from the first build will trigger the cvs rlog and store the results in the database (acting as a cron job). Using ajax will let the client go away while still processing the request on the server.
(0012877)
Julien Jomier   
2008-07-30 10:03   
This has been fixed in 1.0