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
* Add --bls-composing-models config option (#628)
* Added --bls-models to CLI
* Adding unit test
* Fixig typo and updating documentation
* Fix test description
* Adding YAML config BLS test
* Changing to bls_composing_models
* submodel -> composing
* Logic to create BLS composing models for default config (#637)
* Initial changes for profiling BLS
* Removing errant results check-in
* Fixing existing unit tests
* Added unit test to protect default config generation
* Create unchanged BLS composing model output directory (#639)
* Created original name/dir for BLS composing models
* Add clarifying comment
* Fixing typo
* Logic for non-default BLS profiling (#643)
* Initial changes to add non-default BLS configs
* Changing comment
* Adding missing check of top level model config
* BLS Summary Reporting (#648)
* Initial changes for BLS summary reporting
* Fixing and adding golden metrics for BLS
* Adding table manager unit testing for BLS
* BLS Detailed Reporting (#650)
* Add support for BLS detailed reporting
* Fixing copyright issue
* Ensemble -> BLS
* Checking for illegal cases with BLS (#651)
* Checking for illegal cases with BLS
* Fix typo, type checking, and unit test
* Refactor composing model arch (#653)
* Refactor of MRC
* Combined ensemble & bls composing models into a single list. All unit tests passing
* Fix type checking error
* Combining bls/ensemble composing models
* Refactored composing model creation
* Refactoring MRC
* Refactoring of get_next_model_run_config
* Partial refactor of report_manager
* Refactored summary sentence
* Refactored report manager
* Add missing newline
* Updates from review
* Added check to ensure composing models are not ensembles (#656)
* Cleaning up directory writing and ensemble model loading
* Fixing extra dimension bug
* Add BLS documentation (#661)
* Redoing BLS doc changes in new branch
* Changes based on Tim's review
* Getting CodeQL clean!
* Fixing more CodeQL issues
* Another codeQL fix
* Removing more assertTrues
* Fixing fall through (codeQL) warning
Copy file name to clipboardExpand all lines: README.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ limitations under the License.
18
18
19
19
# Triton Model Analyzer
20
20
21
-
Triton Model Analyzer is a CLI tool which can help you find a more optimal configuration, on a given piece of hardware, for single, multiple, or ensemble models running on a [Triton Inference Server](https://github.com/triton-inference-server/server/). Model Analyzer will also generate reports to help you better understand the trade-offs of the different configurations along with their compute and memory requirements.
21
+
Triton Model Analyzer is a CLI tool which can help you find a more optimal configuration, on a given piece of hardware, for single, multiple, ensemble, or BLS models running on a [Triton Inference Server](https://github.com/triton-inference-server/server/). Model Analyzer will also generate reports to help you better understand the trade-offs of the different configurations along with their compute and memory requirements.
22
22
<br><br>
23
23
24
24
# Features
@@ -40,7 +40,10 @@ Triton Model Analyzer is a CLI tool which can help you find a more optimal confi
40
40
### Model Types
41
41
42
42
-[Ensemble Model Search](docs/config_search.md#ensemble-model-search): Model Analyzer can help you find the optimal
43
-
settings when profiling a non-BLS ensemble model, utilizing the [Quick Search](docs/config_search.md#quick-search-mode) algorithm
43
+
settings when profiling an ensemble model, utilizing the [Quick Search](docs/config_search.md#quick-search-mode) algorithm
44
+
45
+
-[BLS Model Search](docs/config_search.md#bls-model-search): Model Analyzer can help you find the optimal
46
+
settings when profiling a BLS model, utilizing the [Quick Search](docs/config_search.md#quick-search-mode) algorithm
44
47
45
48
-[Multi-Model Search](docs/config_search.md#multi-model-search-mode): **EARLY ACCESS** - Model Analyzer can help you
46
49
find the optimal settings when profiling multiple concurrent models, utilizing the [Quick Search](docs/config_search.md#quick-search-mode) algorithm
**Default search mode when profiling non-ensemble models sequentially**
71
+
**Default search mode when profiling non-ensemble/BLS models sequentially**
70
72
71
73
Model Analyzer's brute search mode will do a brute-force sweep of the cross product of all possible configurations. <br>
72
74
It has two modes:
@@ -225,7 +227,7 @@ manual sweep:
225
227
226
228
## Quick Search Mode
227
229
228
-
**Default search mode when profiling ensemble models or multiple models concurrently**
230
+
**Default search mode when profiling ensemble models, BLS models, or multiple models concurrently**
229
231
230
232
This mode uses a hill climbing algorithm to search the configuration space, looking for
231
233
the maximal objective value within the specified constraints. In the majority of cases
@@ -278,8 +280,23 @@ _This mode has the following limitations:_
278
280
- Can only be run in `quick` search mode
279
281
- Only supports up to four composing models
280
282
- Does not support `cpu_only` option for composing models
283
+
- Composing models cannot be ensemble or BLS models
284
+
285
+
Ensemble models can be optimized using the Quick Search mode's hill climbing algorithm to search the composing models' configuration spaces in parallel, looking for the maximal objective value within the specified constraints. Model Analyzer has observed positive outcomes towards finding the maximum objective value; with runtimes under one hour (compared to the days it would take a brute force run to complete) for ensembles that contain up to four composing models.
286
+
287
+
After Model Analyzer has found the best config(s), it will then sweep the top-N configurations found (specified by `--num-configs-per-model`) over the concurrency range before generation of the summary reports.
288
+
289
+
---
290
+
291
+
## BLS Model Search
292
+
293
+
_This mode has the following limitations:_
294
+
295
+
- Can only be run in `quick` search mode
296
+
- Only supports up to four composing models
297
+
- Composing models cannot be ensemble or BLS models
281
298
282
-
Ensemble models can be optimized using the Quick Search mode's hill climbing algorithm to search the ensemble sub-model's configuration spacesin parallel, looking for the maximal objective value within the specified constraints. Model Analyzer has observed positive outcomes towards finding the maximum objective value; with runtimes under one hour (compared to the days it would take a brute force run to complete) for ensembles with up to four composing models.
299
+
BLS models can be optimized using the Quick Search mode's hill climbing algorithm to search the BLS composing models' configuration spaces, as well as the BLS model's instance count, in parallel, looking for the maximal objective value within the specified constraints. Model Analyzer has observed positive outcomes towards finding the maximum objective value; with runtimes under one hour (compared to the days it would take a brute force run to complete) for BLS models that contain up to four composing models.
283
300
284
301
After Model Analyzer has found the best config(s), it will then sweep the top-N configurations found (specified by `--num-configs-per-model`) over the concurrency range before generation of the summary reports.
285
302
@@ -318,7 +335,7 @@ profile_models:
318
335
319
336
### **Model Weighting**
320
337
321
-
In additon to setting a model's objectives or constraints, in multi-model search mode, you have the ability to set a model's weighting. By default each model is set for equal weighting (value of 1), but in the YAML you can specify `weighting: <int>` which will bias that model's objectives when evaluating for an optimal result.
338
+
In addition to setting a model's objectives or constraints, in multi-model search mode, you have the ability to set a model's weighting. By default each model is set for equal weighting (value of 1), but in the YAML you can specify `weighting: <int>` which will bias that model's objectives when evaluating for an optimal result.
0 commit comments