vinitgore commited on
Commit
7f82888
·
verified ·
1 Parent(s): cd34b6c

Update README.md

Browse files
Files changed (1) hide show
  1. README.md +4 -3
README.md CHANGED
@@ -13,8 +13,6 @@ tags:
13
  - low-memory-footprint
14
  ---
15
 
16
- Check this [NPM package](https://github.com/orgs/the-vedantic-coder/packages/npm/stst/580080323) (built for Speech-To-Text usecase) implements the setup and inference for this model. It provides a [React app demo](https://sentence-splitter-poc.vercel.app/) and a `processDirectText` method to try direct inference on text.
17
-
18
  The sentence splitter model is modification of the LSTM model with around 500 B input size taken from the repository: [NNSplit](https://github.com/kornelski/nnsplit)
19
  The size of the model used here is **~4 MB**.
20
 
@@ -35,4 +33,7 @@ No punctuation and no cases (~17% accuracy) <br>
35
  rest is an architectural style that exposes resources via endpoints typically following crud operations each endpoint returns a fixed data structure graphql on the other hand allows clients to specify exactly what data they need in a single query often reducing overfetching and underfetching issues
36
  ```
37
  **Result: 28.90ms ✅**
38
- ![image](https://cdn-uploads.huggingface.co/production/uploads/687852a7f13fbe6c3d4c9974/LrASgi-BmWROVZIUK-36-.png)
 
 
 
 
13
  - low-memory-footprint
14
  ---
15
 
 
 
16
  The sentence splitter model is modification of the LSTM model with around 500 B input size taken from the repository: [NNSplit](https://github.com/kornelski/nnsplit)
17
  The size of the model used here is **~4 MB**.
18
 
 
33
  rest is an architectural style that exposes resources via endpoints typically following crud operations each endpoint returns a fixed data structure graphql on the other hand allows clients to specify exactly what data they need in a single query often reducing overfetching and underfetching issues
34
  ```
35
  **Result: 28.90ms ✅**
36
+ 1. the difference between rest and graphql is explained as follows
37
+ 2. rest is an architectural style that exposes resources via endpoints typically following crud operations
38
+ 3. each endpoint returns a fixed data structure
39
+ 4. graphql on the other hand allows clients to specify exactly what data they need in a single query often reducing overfetching and underfetching issues