Optimize health check response using parallel queries

[souvikghosh04]

Why make this change?

• HealthEndpoint: Parallel Queries to DB #2533
  • Improve health check endpoint performance by running queries in parallel.
  • This allows the health check endpoint to load faster

What is this change?

• Provide option to specify max degree of query parallelism as a config option
• The default value is 4 and max allowed value is 8. System automatically adjusts itself within this range in case a value specified is lower or higher
• .Net framework's Parallel tasks are used to run queries in parallel

Usage

• max-query-parallelism can be set in the config, e.g.: "runtime": { "health": { "max-query-parallelism": 8 } }
• Null value and out of range min-value defaults to 4 and out of range max-value defaults to 8

How was this tested?

• Integration Tests
• Unit Tests

Sample Request(s)

• GET http://localhost:5000/health

[souvikghosh04]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 6 pipeline(s).

[Copilot]

Pull Request Overview

This PR improves the health check endpoint’s performance by parallelizing entity queries and exposing a configurable degree of parallelism.

• Introduce a max-query-parallelism config option (default 4, max 8) with automatic range clamping
• Update HealthCheckHelper to run entity health checks in parallel via Parallel.ForEachAsync
• Add model, converter, constants, and JSON schema entries for the new config

Reviewed Changes

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

Show a summary per file

File	Description
src/Service/HealthCheck/HealthCheckHelper.cs	Parallelize entity health checks and aggregate results
src/Config/ObjectModel/EntityCacheOptions.cs	Define default and limit constants for parallelism
src/Config/HealthCheck/RuntimeHealthCheckConfig.cs	Add MaxQueryParallelism property with default logic
src/Config/Converters/RuntimeHealthOptionsConvertorFactory.cs	Parse and clamp max-query-parallelism from JSON
schemas/dab.draft.schema.json	Add schema definition for max-query-parallelism

Comments suppressed due to low confidence (1)

src/Config/ObjectModel/EntityCacheOptions.cs:39

• [nitpick] The suffix _LIMIT is a bit ambiguous. Consider renaming to DEFAULT_MAX_QUERY_PARALLELISM_MAX for symmetry with DEFAULT_MAX_QUERY_PARALLELISM.

public const int DEFAULT_MAX_QUERY_PARALLELISM_LIMIT = 8;