mirror_js/flexsearch
1
0
Fork 0
mirror of https://github.com/nextapps-de/flexsearch.git synced 2025-08-28 16:20:04 +02:00
Code Issues Releases Wiki Activity

add async resolver readme

Browse Source
This commit is contained in:
Thomas Wilkerling
2025-05-21 19:38:15 +02:00
parent f77de581a8
commit f12b83ec5c
3 changed files with 24 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
doc/resolver-consecutive.svg Normal file
View File

File diff suppressed because one or more lines are too long
Side by Side

After

Width:  |  Height:  |  Size: 20 KiB

3
doc/resolver-parallel.svg Normal file
View File

File diff suppressed because one or more lines are too long
Side by Side

After

Width:  |  Height:  |  Size: 20 KiB

18
doc/resolver.md
View File

@@ -162,6 +162,8 @@ const result = new Resolver({
.resolve(100);
```
## Async Resolver
### Using Async Queries (incl. Runtime Balancer)
All async tasks will run in parallel, balanced by the runtime observer:
@@ -208,6 +210,22 @@ const resolver = await new Resolver({
When tasks are processed consecutively, it will skip specific resolver stages when there is no result expected.
### Compare Parallel VS. Consecutive
When using the parallel workflow, all resolver stages will send their requests (including nested tasks) to the DB immediately and calculate the results in the right order as soon as the request resolves. When the overall workload of your applications has some free resources, a parallel request workflow improves performance compared to the consecutive counterpart.
<p align="center">
<img src="resolver-parallel.svg" width="100%">
</p>
---
When using the consecutive workflow, all resolver stages will send their requests (including nested tasks) to the DB only when the previous request resolves. The advantage of this variant is when a stage becomes invalid because of the previous result, it can skip the request completely and continue with the next stage. This can reduce the overall workload.
<p align="center">
<img src="resolver-consecutive.svg" width="100%">
</p>
<!--
### Custom Resolver