Add scheduler batch size option

[yang-xiaodong]

Summary

• add SchedulerBatchSize option to limit scheduler fetch size
• support the new limit in PostgreSql, MySql, SqlServer, MongoDB, and InMemory storages
• document SchedulerBatchSize in both English and Chinese configuration docs

Testing

• dotnet test --no-restore --verbosity minimal (fails: command not found)

---

https://chatgpt.com/codex/tasks/task_e_68500d907df88320972e9759b7612750

[Copilot]

Pull Request Overview

This PR adds a new SchedulerBatchSize option that limits the number of messages fetched by the scheduler across various storage implementations. Key changes include:

• Introducing a new SchedulerBatchSize property with a default value of 1000 in the CapOptions class.
• Updating SQL queries for SQL Server, PostgreSql, and MySql to use the new batch size limit.
• Adapting the MongoDB and InMemory storage implementations to respect the SchedulerBatchSize value.

Reviewed Changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
src/DotNetCore.CAP/CAP.Options.cs	Added SchedulerBatchSize property with documentation.
src/DotNetCore.CAP.SqlServer/IDataStorage.SqlServer.cs	Updated SQL Server query using SELECT TOP (@batchsize) and added a new parameter.
src/DotNetCore.CAP.PostgreSql/IDataStorage.PostgreSql.cs	Updated PostgreSQL query to include LIMIT @batchsize and added the parameter.
src/DotNetCore.CAP.MySql/IDataStorage.MySql.cs	Updated MySQL query to include LIMIT @batchsize and added the parameter.
src/DotNetCore.CAP.MongoDB/IDataStorage.MongoDB.cs	Modified MongoDB query to limit results based on SchedulerBatchSize.
src/DotNetCore.CAP.InMemoryStorage/IDataStorage.InMemory.cs	Incorporated the batch size option into the LINQ query with .Take().
docs/content/user-guide/zh/cap/configuration.md	Updated documentation with SchedulerBatchSize configuration in Chinese.
docs/content/user-guide/en/cap/configuration.md	Updated documentation with SchedulerBatchSize configuration in English.

Comments suppressed due to low confidence (1)

src/DotNetCore.CAP.MySql/IDataStorage.MySql.cs:246

• Adding an ORDER BY clause to this query would ensure that the limited set of messages is selected in a deterministic order.

… LIMIT @BatchSize {lockSql};

[Copilot]

Consider adding an ORDER BY clause to ensure deterministic message selection when using TOP(@batchsize). This will help guarantee consistent behavior across executions.

[Copilot]

Consider appending an ORDER BY clause to the query to enforce a consistent record order when applying the LIMIT @batchsize.

Suggested change

	$"AND ((\"ExpiresAt\"< @TwoMinutesLater AND \"StatusName\" = '{StatusName.Delayed}') OR (\"ExpiresAt\"< @OneMinutesAgo AND \"StatusName\" = '{StatusName.Queued}')) FOR UPDATE SKIP LOCKED LIMIT @BatchSize;";
	$"AND ((\"ExpiresAt\"< @TwoMinutesLater AND \"StatusName\" = '{StatusName.Delayed}') OR (\"ExpiresAt\"< @OneMinutesAgo AND \"StatusName\" = '{StatusName.Queued}')) FOR UPDATE SKIP LOCKED ORDER BY \"Id\" LIMIT @BatchSize;";

[Copilot]

For the MongoDB query, consider adding a Sort() clause before applying the Limit to ensure predictable results.

Suggested change

	var queryResult = await collection.Find(session, filter)
	var queryResult = await collection.Find(session, filter)
	.Sort(Builders<BsonDocument>.Sort.Ascending("Added")) // Sort by the 'Added' field

[Copilot]

If message order is important in the in-memory implementation, consider sorting the messages before taking the batch to ensure consistency.

Suggested change

	|| (x.StatusName == StatusName.Queued && x.ExpiresAt < DateTime.Now.AddMinutes(-1)))
	|| (x.StatusName == StatusName.Queued && x.ExpiresAt < DateTime.Now.AddMinutes(-1)))
	.OrderBy(x => x.ExpiresAt)