You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/200-installation.yml
+3-3
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ body:
7
7
- type: markdown
8
8
attributes:
9
9
value: >
10
-
#### Before submitting an issue, please make sure the issue hasn't been already addressed by searching through [the existing and past issues](https://github.com/project-metron/metron/issues?q=is%3Aissue+sort%3Acreated-desc+).
10
+
#### Before submitting an issue, please make sure the issue hasn't been already addressed by searching through [the existing and past issues](https://github.com/project-etalon/etalon/issues?q=is%3Aissue+sort%3Acreated-desc+).
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/300-usage.yml
+5-5
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,13 @@
1
1
name: 💻 Usage
2
-
description: Raise an issue here if you don't know how to use Metron.
2
+
description: Raise an issue here if you don't know how to use etalon.
3
3
title: "[Usage]: "
4
4
labels: ["usage"]
5
5
6
6
body:
7
7
- type: markdown
8
8
attributes:
9
9
value: >
10
-
#### Before submitting an issue, please make sure the issue hasn't been already addressed by searching through [the existing and past issues](https://github.com/project-metron/metron/issues?q=is%3Aissue+sort%3Acreated-desc+).
10
+
#### Before submitting an issue, please make sure the issue hasn't been already addressed by searching through [the existing and past issues](https://github.com/project-etalon/etalon/issues?q=is%3Aissue+sort%3Acreated-desc+).
11
11
- type: textarea
12
12
attributes:
13
13
label: Your current environment
@@ -17,11 +17,11 @@ body:
17
17
required: true
18
18
- type: textarea
19
19
attributes:
20
-
label: How would you like to use Metron
20
+
label: How would you like to use etalon
21
21
description: |
22
-
A detailed description of how you want to use Metron.
22
+
A detailed description of how you want to use etalon.
23
23
value: |
24
-
I want to run inference of a [specific inference engine](put link here). I don't know how to integrate it with Metron.
24
+
I want to run inference of a [specific inference engine](put link here). I don't know how to integrate it with etalon.
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/400-bug report.yml
+1-1
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ body:
7
7
- type: markdown
8
8
attributes:
9
9
value: >
10
-
#### Before submitting an issue, please make sure the issue hasn't been already addressed by searching through [the existing and past issues](https://github.com/project-metron/metron/issues?q=is%3Aissue+sort%3Acreated-desc+).
10
+
#### Before submitting an issue, please make sure the issue hasn't been already addressed by searching through [the existing and past issues](https://github.com/project-etalon/etalon/issues?q=is%3Aissue+sort%3Acreated-desc+).
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/500-feature request.yml
+2-2
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,13 @@
1
1
name: 🚀 Feature request
2
-
description: Submit a proposal/request for a new Metron feature
2
+
description: Submit a proposal/request for a new etalon feature
3
3
title: "[Feature]: "
4
4
labels: ["feature request"]
5
5
6
6
body:
7
7
- type: markdown
8
8
attributes:
9
9
value: >
10
-
#### Before submitting an issue, please make sure the issue hasn't been already addressed by searching through [the existing and past issues](https://github.com/project-metron/metron/issues?q=is%3Aissue+sort%3Acreated-desc+).
10
+
#### Before submitting an issue, please make sure the issue hasn't been already addressed by searching through [the existing and past issues](https://github.com/project-etalon/etalon/issues?q=is%3Aissue+sort%3Acreated-desc+).
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/600-RFC.yml
+1-1
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ body:
7
7
- type: markdown
8
8
attributes:
9
9
value: >
10
-
#### Please take a look at previous [RFCs](https://github.com/project-metron/metron/issues?q=label%3ARFC+sort%3Aupdated-desc) for reference.
10
+
#### Please take a look at previous [RFCs](https://github.com/project-etalon/etalon/issues?q=label%3ARFC+sort%3Aupdated-desc) for reference.
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/800-misc discussion.yml
+3-3
Original file line number
Diff line number
Diff line change
@@ -7,12 +7,12 @@ body:
7
7
- type: markdown
8
8
attributes:
9
9
value: >
10
-
#### Before submitting an issue, please make sure the issue hasn't been already addressed by searching through [the existing and past issues](https://github.com/project-metron/metron/issues?q=is%3Aissue+sort%3Acreated-desc+).
10
+
#### Before submitting an issue, please make sure the issue hasn't been already addressed by searching through [the existing and past issues](https://github.com/project-etalon/etalon/issues?q=is%3Aissue+sort%3Acreated-desc+).
Copy file name to clipboardExpand all lines: .github/PULL_REQUEST_TEMPLATE.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ FIX #xxxx (*link existing issues this PR will resolve*)
10
10
<!-- inside this <details> section, markdown rendering does not work, so we use raw html here. -->
11
11
<summary><b> PR Checklist (Click to Expand) </b></summary>
12
12
13
-
<p>Thank you for your contribution to Metron! Before submitting the pull request, please ensure the PR meets the following criteria. This helps Metron maintain the code quality and improve the efficiency of the review process.</p>
13
+
<p>Thank you for your contribution to etalon! Before submitting the pull request, please ensure the PR meets the following criteria. This helps etalon maintain the code quality and improve the efficiency of the review process.</p>
14
14
15
15
<h3>PR Title and Classification</h3>
16
16
<p>Only specific types of PRs will be reviewed. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:</p>
@@ -32,15 +32,15 @@ FIX #xxxx (*link existing issues this PR will resolve*)
32
32
<ul>
33
33
<li>Pass all linter checks. Please use <code>make format</code></a> to format your code.</li>
34
34
<li>The code need to be well-documented to ensure future contributors can easily understand the code.</li>
35
-
<li>Please add documentation to <code>docs/source/</code> if the PR modifies the user-facing behaviors of Metron. It helps user understand and utilize the new features or changes.</li>
35
+
<li>Please add documentation to <code>docs/source/</code> if the PR modifies the user-facing behaviors of etalon. It helps user understand and utilize the new features or changes.</li>
36
36
</ul>
37
37
38
38
<h3>Notes for Large Changes</h3>
39
39
<p>Please keep the changes as concise as possible. For major architectural changes (>500 LOC), we would expect a GitHub issue (RFC) discussing the technical design and justification. Otherwise, we will tag it with <code>rfc-required</code> and might not go through the PR.</p>
40
40
41
41
<h3>Thank You</h3>
42
42
43
-
<p> Finally, thank you for taking the time to read these guidelines and for your interest in contributing to Metron. Your contributions make Metron a great tool for everyone! </p>
43
+
<p> Finally, thank you for taking the time to read these guidelines and for your interest in contributing to etalon. Your contributions make etalon a great tool for everyone! </p>
There are many more arguments for running benchmark, run the following to know more:
83
83
```bash
84
-
python -m metron.run_benchmark -h
84
+
python -m etalon.run_benchmark -h
85
85
```
86
86
87
87
### Running with Open Source Systems
88
-
Metron can be run with any open source LLM inference system. If open source system does not provide OpenAI Compatible APIs, then kindly implement new LLM clients to support new open source system as explained in [here](#implementing-new-llm-clients).
88
+
etalon can be run with any open source LLM inference system. If open source system does not provide OpenAI Compatible APIs, then kindly implement new LLM clients to support new open source system as explained in [here](#implementing-new-llm-clients).
89
89
90
90
Here we give an example with vLLM.
91
91
@@ -109,11 +109,11 @@ And then we can run the benchmark as shown [here](#running-benchmark). Be sure t
109
109
The results of the benchmark are saved in the results directory specified by the `--output-dir` argument.
110
110
111
111
## Running Prefill Profiler
112
-
To profile prefill times of open source systems and create a prefill time predictor for a given model and open source system, based on input prompt length, we can run `metron.prefill_profiler`.
112
+
To profile prefill times of open source systems and create a prefill time predictor for a given model and open source system, based on input prompt length, we can run `etalon.prefill_profiler`.
113
113
114
114
Launch any open source system and setup API keys and URL as shown for [vLLM](#running-with-open-source-systems).
title={etalon: Holistic Performance Evaluation Framework for LLM Inference Systems},
171
171
author={Amey Agrawal and Anmol Agarwal and Nitin Kedia and Jayashree Mohan and Souvik Kundu and Nipun Kwatra and Ramachandran Ramjee and Alexey Tumanov},
Copy file name to clipboardExpand all lines: docs/guides/guide.rst
+1-1
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
Guides
2
2
======
3
3
4
-
This section contains additional topics and features that are not covered in the :doc:`../how_to_use` section. These guides are meant to provide a deeper understanding of the library and its features, and help in getting the most out of the ``metron``.
4
+
This section contains additional topics and features that are not covered in the :doc:`../how_to_use` section. These guides are meant to provide a deeper understanding of the library and its features, and help in getting the most out of the ``etalon``.
0 commit comments