Skip to content

Commit

Permalink
docs: Fixed latency section of the README (#178)
Browse files Browse the repository at this point in the history
* docs: Fixed typo in latency section of the README

* docs: Fixed typo
  • Loading branch information
frgfm authored Nov 23, 2021
1 parent 21f3adb commit edcb146
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -80,7 +80,7 @@ Reference scripts are provided to train your models using holocron on famous pub

You crave for SOTA performances, but you don't know whether it fits your needs in terms of latency?

In the table below, you will find a latency benchmark (forward pass not included) for all supported models:
In the table below, you will find a latency benchmark for all supported models:

| Arch | GPU mean (std) | CPU mean (std) |
| ------------------------------------------------------------ | ----------------- | ------------------ |
Expand Down Expand Up @@ -114,7 +114,7 @@ In the table below, you will find a latency benchmark (forward pass not included

This benchmark was performed over 100 iterations on (224, 224) inputs, on a laptop to better reflect performances that can be expected by common users. The hardware setup includes an [Intel(R) Core(TM) i7-10750H](https://ark.intel.com/content/www/us/en/ark/products/201837/intel-core-i710750h-processor-12m-cache-up-to-5-00-ghz.html) for the CPU, and a [NVIDIA GeForce RTX 2070 with Max-Q Design](https://www.nvidia.com/fr-fr/geforce/graphics-cards/rtx-2070/) for the GPU.

You can run this latency benchmark for any CAM method on your hardware as follows:
You can run this latency benchmark for any model on your hardware as follows:

```bash
python scripts/eval_latency.py rexnet1_0x
Expand Down

0 comments on commit edcb146

Please sign in to comment.