You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Workflow-core version 3.7.0 was put under test to evaluate its performance. The setup used was single node with the default MemoryPersistenceProvider persistence provider.
4
+
5
+
## Methodology
6
+
7
+
- Test Environment - Test were run on following two environments one after the other to see how workflow-core performance with a lower vs higher hardware configuration.
- Test Workflow: Workflow consist of 3 basic steps. These 3 simple steps were chosen to test the performance of the workflow engine with minimal yet sufficient complexity and to avoid any external dependencies.
19
+
- Step1 : Generate a [random number](https://learn.microsoft.com/dotnet/api/system.random?view=net-6.0) between 1 to 10 and print it on standard output.
- Step 2.1: If value generate in step1 is > 5 then print it on standard output.
22
+
- Step 2.2: If value generate in step1 is <= 5 then print it on standard output.
23
+
- Step3: Prints a good bye message on standard output.
24
+
- Test tools:
25
+
-[NBomber](https://nbomber.com/docs/getting-started/overview/) was used as performance testing framework with C# console app as base.
26
+
27
+
- Test scenarios:
28
+
- Each type of test run executed for 20 minutes.
29
+
- NBomber Load Simulation of type [KeepConstant](https://nbomber.com/docs/using-nbomber/basic-api/load-simulation#keep-constant) copies was used. This type of simulation keep a constant amount of Scenario copies(instances) for a specific period.
30
+
- Concurrent copies [1,2,3,4,5,6,7,8,10,12,14,16,32,64,128,256,512,1024] were tested.
31
+
- For example if we take Concurrent copies=4 and Duration=20 minutes this means that NBomber will ensure that we have 4 instance of Test Workflow running in parallel for 20 minutes.
32
+
33
+
## Results
34
+
35
+
- Workflow per seconds - Below tables shows how many workflows we are able to execute per second on two different environment with increasing number of concurrent copies.
Copy file name to clipboardExpand all lines: src/providers/WorkflowCore.Providers.AWS/README.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,6 +34,18 @@ services.AddWorkflow(cfg =>
34
34
If any AWS resources do not exists, they will be automatcially created. By default, all DynamoDB tables and indexes will be provisioned with a throughput of 1, you can modify these values from the AWS console.
35
35
You may also specify a prefix for the dynamo table names.
36
36
37
+
If you have a preconfigured dynamoClient, you can pass this in instead of the credentials and config
0 commit comments