Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2024.01.10 #17

Closed
6 of 14 tasks
seanmcilroy29 opened this issue Jan 8, 2024 · 1 comment
Closed
6 of 14 tasks

2024.01.10 #17

seanmcilroy29 opened this issue Jan 8, 2024 · 1 comment
Assignees

Comments

@seanmcilroy29
Copy link
Contributor

seanmcilroy29 commented Jan 8, 2024


2024.01.10 Agenda/Minutes


Time: Bi-weekly @ 1600 (GMT) - See the time in your timezone

  • Co-Chair - Marco Valtas (Thoughtsworks)
  • Co-Chair - Chris Xie- (Futurewei)
  • Convener – Sean Mcilroy (Linux Foundation)

Antitrust Policy

Joint Development Foundation meetings may involve participation by industry competitors, and the Joint Development Foundation intends to conduct all of its activities in accordance with applicable antitrust and competition laws. It is, therefore, extremely important that attendees adhere to meeting agendas and be aware of and not participate in any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws.

If you have questions about these matters, please contact your company counsel or counsel to the Joint Development Foundation, DLA Piper.

Recordings

WG agreed to record all Meetings. This meeting recording will be available until the next scheduled meeting.
Meeting recording link

Roll Call

Please add 'Attended' to this issue during the meeting to denote attendance.

Any untracked attendees will be added by the GSF team below:

  • Full Name, Affiliation, (optional) GitHub username

Agenda

  • Approve agenda
  • Approve previous Meeting Minutes

Introductions

  • Any new members?

Submitted Issues

Summary

Spec Development Proposal and focus areas

Software energy consumption ratings.

  • Concern about software ratings being affected by hardware variations.
  • Inconsistency in energy efficiency across different hardware manufacturers should be addressed in the spec.
  • Importance of standardising test environments for software ratings, including a baseline hardware setup.

Standardizing software testing environments.

  • Standardizing the test environment to remove variability in energy consumption and carbon emissions.
  • Feasibility of the GSF standardisation efforts and the potential for other organisations to duplicate their testing environment.
  • Oracle and Microsoft adopt similar testing standards for machine learning performance despite wide variations in software capabilities.

Software categorization and commonality.

  • Standardizing standard components of education to create domain-specific software specifications.
  • Standard software categorization and its relationship to performance.
  • Process for defining commonalities in software categorization, using examples from different industries.

Benchmark certification for software.

  • Define benchmark certification as a standardized workload or test on software, with consistent test environment specifications for comparison.
  • Standardized certification process for music streaming services.
  • Potential concerns with the rating system, with a standard platform for measuring hardware performance.

Standardizing GPU performance measurement.

  • Proposed baseline for measuring GPU performance
  • Creating an open-source product for crowd-sourced testing and rating of software, potentially leading to a governing body for GSF. The idea is to provide an intuitive, non-numerical way for people to evaluate software based on their experiences and opinions.

Standardizing and certifying software performance metrics.

  • Potential approaches for rating and approving energy-efficient products, including a community-based approach and a more formalised body to govern ratings.
  • Identifying standard components in upcoming events to improve efficiency while comparing the situation to the SCI specification for measurement, noting that it's complex and requires expertise.
  • The need for a conformance program to validate scores in the context of a hypothetical "go cup" for the computing community.
  • Two approaches to getting a trustworthy number for a product's performance: official testing by a highway authority and customer-generated data using a benchmarking tool.

Spec Review

  • Proposal to discuss the Spec updates at the next WG meeting?

AOB

  • Member submissions

Future meeting Agenda submissions

Next Meeting

  • 24th Jan @ 9 am P/T

Adjourn

  • Motion to adjourn

Meeting Action Items / Standing Agenda / Future Agenda submissions

  • Add here
@seanmcilroy29
Copy link
Contributor Author

Approved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants