📝 Typo correction and Grammatical in the features
and installation
documentation page (#355)
* 📝 docs: Fix typos in the `features` documentation page (#355) * 📝 docs: Fix typos in the `installation` documentation page (#355)
This commit is contained in:
parent
6963d00074
commit
5301d09894
2 changed files with 35 additions and 35 deletions
|
@ -8,11 +8,11 @@ The different caching features provided are as follows:
|
|||
- In memory cache
|
||||
- Hybrid cache
|
||||
|
||||
## Explaination
|
||||
## Explanation
|
||||
|
||||
### No Cache
|
||||
|
||||
This feature can drastically reduce binary size but with the cost that subsequent search requests and previous & next page search results are not cached which can make navigating between pages slower. As well as page refreshes of the same page also becomes slower as each refresh has to fetch the results from the upstream search engines.
|
||||
This feature can drastically reduce binary size but with the cost that subsequent search requests and previous & next page search results are not cached which can make navigating between pages slower. As well as Page refreshes of the same page also become slower as each refresh has to fetch the results from the upstream search engines.
|
||||
|
||||
### Redis Cache
|
||||
|
||||
|
@ -20,11 +20,11 @@ This feature allows the search engine to cache the results on the redis server.
|
|||
|
||||
### In Memory Cache
|
||||
|
||||
This feature is the default feature provided by the project. This feature allows the search engine to cache the results in the memory which can help increase the speed of the fetched cache results and it also has an advantage that it is extremely reliable as all the results are stored in memory within the search engine. Though the disadvantage of this solution are that caching of results is slightly slower than the `redis-cache` solution, it requires a good amount of memory on the system and as such is not ideal for very low memory devices and is highly unscalable.
|
||||
This feature is the default feature provided by the project. This feature allows the search engine to cache the results in the memory which can help increase the speed of the fetched cache results and it also has the advantage that it is extremely reliable as all the results are stored in memory within the search engine. Though the disadvantage of this solution is that caching of results is slightly slower than the `redis-cache` solution, it requires a good amount of memory on the system and as such is not ideal for very low memory devices and is highly unscalable.
|
||||
|
||||
### Hybrid Cache
|
||||
|
||||
This feature provides the advantages of both `In Memory` caching and `Redis` caching and it is an ideal solution if you need a very resiliant and reliable solution for the `Websurfx` which can provide both speed and reliability. Like for example if the `Redis` server becomes unavailable then the search engine switches to `In Memory` caching until the server becomes available again. This solution can be useful for hosting `Websurfx` instance which will be used by hundreds or thousands of users over the world.
|
||||
This feature provides the advantages of both `In Memory` caching and `Redis` caching and it is an ideal solution if you need a very resilient and reliable solution for the `Websurfx` which can provide both speed and reliability. Like for example if the `Redis` server becomes unavailable then the search engine switches to `In Memory` caching until the server becomes available again. This solution can be useful for hosting a `Websurfx` instance which will be used by hundreds or thousands of users all over the world.
|
||||
|
||||
## Tabular Summary
|
||||
|
||||
|
@ -34,7 +34,7 @@ This feature provides the advantages of both `In Memory` caching and `Redis` cac
|
|||
| **Speed** | Fast | Caching is slow, but retrieval of cache data is fast | Slow | Fastest |
|
||||
| **Reliability** | ✅ | ✅ | ✅ | ❌ |
|
||||
| **Scalability** | ✅ | ❌ | - | ✅ |
|
||||
| **Resiliancy** | ✅ | ✅ | ✅ | ❌ |
|
||||
| **Resiliency** | ✅ | ✅ | ✅ | ❌ |
|
||||
| **Production/Large Scale/Instance use** | ✅ | Not Recommended | Not Recommended | Not Recommended |
|
||||
| **Low Memory Support** | ❌ | ❌ | ✅ | ❌ |
|
||||
| **Binary Size** | Big | Bigger than `No Cache` | small | Bigger than `No Cache` |
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue