Azure / Azure/data-api-builder
Optimize how the additional row in paginated result is chopped off
Open
enhancement
graphql
perf
- Dominant language
- C#
- Stars
- 1.5k
- Forks
- 370
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 8
Description
These rootEnumerated.Count() and rootEnumerated.ToArray() could be optimized ... we actually could allocate a list and then chop the list and would fare better.
_Originally posted by @michaelstaib in https://github.com/Azure/data-api-builder/pull/1392#discussion_r1163208354_
Contributor guide
Assessment
This issue has not been assessed yet.