Closed Bug 1383901 Opened 2 years ago Closed Yesterday

make a simpler tool to compare memory profiles from AWSY

Categories

(Tree Management :: Perfherder, enhancement, P3)

enhancement

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: jmaher, Unassigned)

References

Details

perfherder has continued to provide much value and continues to be a source of truth for many.  AWSY has a lot of great data and is fully integrated into our sheriffing model from perfherder alerts.

One concern that developers have is being able to easily diff the data between one revision and the next.  There are some instructions in bug 1376105 comment 4, but those are a bit hacky- it would be great to do this automatic or in a much simpler manner.

I see perfherder as being able to find a current artifact and a previous artifact- then there would be work to display the differences (probably taking about memory code and allowing it to support two revisions- or copying parts of it to build a viewer inside of perfherder.  One other thought is perfherder could build a .json object with both artifacts and the end user will be prompted to download.
I filed a similar bug with respect to the new compiler warning measures. In general there seems to be a need/desire for custom tools to interpret the perfherder data in domain specific ways (ala the reftest analyzer), it would be great if we could provide support for this at an API level so that submitters could plug stuff in specific to their performance framework.
See Also: → 1367579
Priority: -- → P3

(In reply to Joel Maher ( :jmaher ) (UTC-4) from comment #0)

[...]
One concern that developers have is being able to easily diff the data
between one revision and the next. There are some instructions in bug
1376105 comment 4, but those are a bit hacky- it would be great to do this
automatic or in a much simpler manner.
[...]

Hi, Eric! Are these steps still up to date or have they evolved? Has any non-Perfherder tool been built which aids in providing this diff data?
Thanks!

Flags: needinfo?(erahm)

(In reply to Ionuț Goldan [:igoldan], Performance Sheriff from comment #2)

Hi, Eric! Are these steps still up to date or have they evolved? Has any non-Perfherder tool been built which aids in providing this diff data?
Thanks!

Those steps are still correct. about:memory has support for diffing, but we would definitely prefer to be able to do this directly in perfherder.

Flags: needinfo?(erahm)

I'm adding this ticket to our roadmap, but closing this as it's more than 18 months olds.
We don't have it on radar for Q1/2020, but will reconsider it for the following quarters.

Status: NEW → RESOLVED
Closed: Yesterday
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.