Closed Bug 1976784 Opened 1 year ago Closed 10 months ago

Llama.cpp native peformance test

Categories

(Core :: Machine Learning: General, enhancement)

enhancement

Tracking

()

RESOLVED FIXED
144 Branch
Tracking Status
firefox144 --- fixed

People

(Reporter: atossou, Assigned: atossou, NeedInfo)

References

Details

(Whiteboard: [ai-runtime])

Attachments

(1 file, 1 obsolete file)

Llama.cpp performance test

Attachment #9505410 - Attachment is obsolete: true
Attachment #9499953 - Attachment description: WIP: Bug 1976784 - Llama.cpp native peformance test r?tarek,padenot → Bug 1976784 - Llama.cpp native peformance test r?tarek,padenot
Status: ASSIGNED → RESOLVED
Closed: 11 months ago
Resolution: --- → FIXED
Target Milestone: --- → 144 Branch

Hi Aristide! There was a build_metrics regression detected on the push mentioned below, and this bug was referenced. Do you think this bug may have caused the performance regression ?

Perfherder has detected a build_metrics performance change from push 347c59ae0bce3cde618bb738c6e630896f22cf8a. As author of one of the patches included in that push, we need your help to address this regression.

Please acknowledge, and begin investigating this alert within 3 business days, or the patch(es) may be backed out in accordance with our regression policy. Our guide to handling regression bugs has information about how you can proceed with this investigation.

If you have any questions or need any help with the investigation, please reach out to a performance sheriff. Alternatively, you can find help on Slack by joining #perf-help, and on Matrix you can find help by joining #perftest.

Regressions:

Ratio Test Platform Options Absolute values (old vs new)
6% compiler_metrics num_static_constructors osx-cross 91.00 -> 96.50
4% compiler_metrics num_static_constructors linux64-shippable 102.00 -> 106.17

Details of the alert can be found in the alert summary, including links to graphs and comparisons for each of the affected tests.

If you need the profiling jobs you can trigger them yourself from treeherder job view or ask a performance sheriff to do that for you.

You can run all of these tests on try with ./mach try perf --alert 46416

The following documentation link provides more information about this command.

Status: REOPENED → RESOLVED
Closed: 11 months ago10 months ago
Resolution: --- → FIXED
Target Milestone: --- → 144 Branch
QA Whiteboard: [qa-triage-done-c145/b144]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: