Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Question] Best practices for using SQL Persistance #1327

Open
ljcbn opened this issue Jan 3, 2025 · 1 comment
Open

[Question] Best practices for using SQL Persistance #1327

ljcbn opened this issue Jan 3, 2025 · 1 comment

Comments

@ljcbn
Copy link

ljcbn commented Jan 3, 2025

Hello,

We are using Workflow Core to launch and manage a lot of complex workflows. For this, we are using SQL Persitance Data.
Unfortunally, we are encountenring some performance issue. Our workflow host seems crash due to the amount of data (around 3000 workflows are working concurrencely) and stoppes.

What are the best pratictices that we could use on our database and workflow host to fix it ?

Thanks,

@ljcbn
Copy link
Author

ljcbn commented Jan 6, 2025

We are adding workflow core with this into Program.cs in our webservice hosting our workflow host with the following code :

var configuration = new ConfigurationBuilder()
.SetBasePath(Directory.GetCurrentDirectory())
.AddJsonFile("appsettings.json")
.Build();

builder.Services.AddWorkflow(x => x.UseSqlServer(configuration.GetConnectionString("SQLPersistence"), true, true));

The problem seems to be a cached problem with too much object managed by the host

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant