Closed Bug 650382 Opened 13 years ago Closed 13 years ago

Update endurance results dashboard to use pre-calculated values for min/max/average

Categories

(Mozilla QA Graveyard :: Mozmill Result Dashboard, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: davehunt, Assigned: davehunt)

References

Details

Attachments

(1 file, 3 obsolete files)

Use the new pre-calculated values stored in the report rather than working this out on the client-side.
Assignee: nobody → dave.hunt
Attachment #526405 - Flags: review?(anthony.s.hughes)
Attachment #526405 - Flags: review?(anthony.s.hughes) → review+
Attachment #526405 - Flags: review?(hskupin)
Comment on attachment 526405 [details] [diff] [review]
Use pre-calculated values from report. v1

>-              minAllocatedMemory : min(testAllocatedMemoryResults),
>-              maxAllocatedMemory : max(testAllocatedMemoryResults),
>-              averageAllocatedMemory : Math.round(average(testAllocatedMemoryResults)),
>-              minMappedMemory : min(testMappedMemoryResults),
>-              maxMappedMemory : max(testMappedMemoryResults),
>-              averageMappedMemory : Math.round(average(testMappedMemoryResults))

Please also remove the declaration for those array variables which hold the data. Otherwise looks fine.
Attachment #526405 - Flags: review?(hskupin) → review-
(In reply to comment #2)
> Comment on attachment 526405 [details] [diff] [review] [review]
> Use pre-calculated values from report. v1
> 
> >-              minAllocatedMemory : min(testAllocatedMemoryResults),
> >-              maxAllocatedMemory : max(testAllocatedMemoryResults),
> >-              averageAllocatedMemory : Math.round(average(testAllocatedMemoryResults)),
> >-              minMappedMemory : min(testMappedMemoryResults),
> >-              maxMappedMemory : max(testMappedMemoryResults),
> >-              averageMappedMemory : Math.round(average(testMappedMemoryResults))
> 
> Please also remove the declaration for those array variables which hold the
> data. Otherwise looks fine.

Thanks for spotting that, it should be a bit cleaner now.
Attachment #526405 - Attachment is obsolete: true
Attachment #529956 - Flags: review?(hskupin)
Comment on attachment 529956 [details] [diff] [review]
Use pre-calculated values from report. v1.1

I think it's fine now. Lets wait for the other patches to get checked-in.
Attachment #529956 - Flags: review?(hskupin) → review+
Blocks: 657508
A Pivotal Tracker story has been created for this Bug: https://www.pivotaltracker.com/story/show/13565931
Henrik Skupin changed story state to started in Pivotal Tracker
Henrik Skupin changed story state to unstarted in Pivotal Tracker
Updated to support reports that don't include the pre-calculated stats. Metrics will be output as "--" on this older reports.
Attachment #529956 - Attachment is obsolete: true
Attachment #535672 - Flags: review?(hskupin)
Comment on attachment 535672 [details] [diff] [review]
Use pre-calculated values from report. v2.0

>+          value.min_allocated_memory = (value.stats && value.stats.allocated) ? Math.round(value.stats.allocated.min * BYTE_TO_MEGABYTE) : METRIC_UNAVAILABLE;

For old reports which do not pre-calculate the metrics there will be no stats property. Why can't we simply check it once at the beginning? That way we wouldn't have to run the same check again and again. Why do you have an extra check for stats.allocated?
I'm checking for stats.allocated because results from Firefox 6+ will have the explicit and resident values, and not allocated or mapped.
I was hoping that you cover that in the patch on bug 657508, so we do not mix those different features. It would also make problems if we would have to back-out this specific patch.
(In reply to comment #11)
> I was hoping that you cover that in the patch on bug 657508, so we do not
> mix those different features. It would also make problems if we would have
> to back-out this specific patch.

Updated patch with suggestions.
Attachment #535672 - Attachment is obsolete: true
Attachment #535672 - Flags: review?(hskupin)
Attachment #536309 - Flags: review?(hskupin)
Comment on attachment 536309 [details] [diff] [review]
Use pre-calculated values from report. v2.1

Looks good. Go ahead and land it.
Attachment #536309 - Flags: review?(hskupin) → review+
Landed as:
https://github.com/whimboo/mozmill-dashboard/commit/bac9de248fad62d96a648a5a3dbf71e8f74c98ed
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: