Pricing
Pay per usage
Kv To Kv Orchestrator
Run actors/tasks from items in a KvStore and save results in another
Pricing
Pay per usage
Rating
0.0
(0)
Developer
Actor stats
0
Bookmarked
2
Total users
0
Monthly active users
a month ago
Last modified
Categories
Share
Actor Orchestrator (KV to KV)
Give it a KV store with keys and values, and it will run an actor/task for each key with its contents as input then save it to another store.
This actor is pretty lightweight, so it should be able to run on 128MB of memory for as long as you need without any problems.
Behavior
- Reads all keys from the input store
- Calculates the number of concurrent runs based on the available memory for you as a user and the
maxConcurrencyinput. It will try to use half of all the maximum memory. - Creates an amount of concurrent runs, each running the actor/task for a key from the input store.
- When a run finishes, it saves the result to the output store.
- When a run fails, it logs the error to its dataset.
- When all runs are finished, it exits.
It keeps track of the current status of each run in a key-value store. So if you restart it or it migrates, it will pick up where it left off.
Common usage
- Set up a named KV store for the inputs.
- Push data to be processed to the KV store.
- Set up a named KV store for the results.
- Run the actor.
You can also set up this actor to run on a schedule. (Recommended) Remember to not have more than one run of this actor running at the same time.
