Card: size and speed (measured, incl. Bev-Pro-C on one H200)
Browse files- .gitattributes +1 -0
- README.md +23 -3
- assets/size.png +0 -0
- assets/speed.png +3 -0
.gitattributes
CHANGED
|
@@ -34,3 +34,4 @@ saved_model/**/* filter=lfs diff=lfs merge=lfs -text
|
|
| 34 |
*.zst filter=lfs diff=lfs merge=lfs -text
|
| 35 |
*tfevents* filter=lfs diff=lfs merge=lfs -text
|
| 36 |
assets/automation.png filter=lfs diff=lfs merge=lfs -text
|
|
|
|
|
|
| 34 |
*.zst filter=lfs diff=lfs merge=lfs -text
|
| 35 |
*tfevents* filter=lfs diff=lfs merge=lfs -text
|
| 36 |
assets/automation.png filter=lfs diff=lfs merge=lfs -text
|
| 37 |
+
assets/speed.png filter=lfs diff=lfs merge=lfs -text
|
README.md
CHANGED
|
@@ -123,10 +123,11 @@ model = bev.load("sathiskumarjothi0/Bev-Large-C", device="mps") # Apple Silic
|
|
| 123 |
|
| 124 |
Command line: `bev "I was charged twice, please refund" --noul "Does the customer ask for a refund?" --device cpu`.
|
| 125 |
|
| 126 |
-
| Device
|
| 127 |
|---|---|---|
|
| 128 |
-
| CPU only | about 25 s | about 0.18 s |
|
| 129 |
-
| Apple GPU (`mps`) | about 22 s | about 0.05 s |
|
|
|
|
| 130 |
|
| 131 |
The first load includes reading the 1.6 GB weights; after that, use `decide_batch` for many documents.
|
| 132 |
|
|
@@ -240,6 +241,25 @@ best in the row; – = not run. * = an area Bev was not built for.
|
|
| 240 |
| Legal case holdings* | 42.0 | 71.2 | **77.6** | 69.2 | 72.2 | 61.2 | 71.6 | 55.0 |
|
| 241 |
|
| 242 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 243 |
### How much of the work can you automate?
|
| 244 |
|
| 245 |

|
|
|
|
| 123 |
|
| 124 |
Command line: `bev "I was charged twice, please refund" --noul "Does the customer ask for a refund?" --device cpu`.
|
| 125 |
|
| 126 |
+
| Device | First load | One document with 3 questions |
|
| 127 |
|---|---|---|
|
| 128 |
+
| Apple M4 Pro laptop, CPU only | about 25 s | about 0.18 s |
|
| 129 |
+
| Apple M4 Pro laptop, GPU (`mps`) | about 22 s | about 0.05 s |
|
| 130 |
+
| One NVIDIA H200 GPU (`cuda`) | about 32 s | about 0.015 s |
|
| 131 |
|
| 132 |
The first load includes reading the 1.6 GB weights; after that, use `decide_batch` for many documents.
|
| 133 |
|
|
|
|
| 241 |
| Legal case holdings* | 42.0 | 71.2 | **77.6** | 69.2 | 72.2 | 61.2 | 71.6 | 55.0 |
|
| 242 |
|
| 243 |
|
| 244 |
+
### Size and speed
|
| 245 |
+
|
| 246 |
+

|
| 247 |
+
|
| 248 |
+
Accuracy on the same 10,238 answers against total parameters (log scale), for every system with a published size:
|
| 249 |
+
Bev-Large-C (0.4B) and Bev-Pro-C (25.8B) are more accurate than LLMs of 31B to 675B.
|
| 250 |
+
|
| 251 |
+

|
| 252 |
+
|
| 253 |
+
| Bev, one document with 3 questions (package from PyPI) | Per decision | In batches of 64 |
|
| 254 |
+
|---|---|---|
|
| 255 |
+
| Bev-Large-C, one NVIDIA H200 GPU | 4.9 ms | 3.4 ms |
|
| 256 |
+
| Bev-Large-C, Apple M4 Pro laptop GPU | 17 ms | |
|
| 257 |
+
| Bev-Large-C, Apple M4 Pro laptop CPU | 60 ms | |
|
| 258 |
+
| Bev-Pro-C, one NVIDIA H200 GPU | 22 ms | 7.8 ms |
|
| 259 |
+
|
| 260 |
+
The LLMs and Jev were measured through their cloud APIs (median response time per decision, including network and
|
| 261 |
+
queueing): Jev 98 ms, the five LLMs 4.1 to 7.0 s.
|
| 262 |
+
|
| 263 |
### How much of the work can you automate?
|
| 264 |
|
| 265 |

|
assets/size.png
ADDED
|
assets/speed.png
ADDED
|
Git LFS Details
|