Azure / Azure/azure-functions-host
Optimize admin/instance/assign endpoint.
- Dominant language
- C#
- Stars
- 2k
- Forks
- 482
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 38
Description
This is an endpoint which gets called as part of specialization on Linux SKUs, so this impacts cold start latency.
Some easy wins:
Switch to STJ deserialization with source generated metadata. ( I spotted atleast 1 deserialization and 1 serialization calls)
https://github.com/Azure/azure-functions-host/blob/e5bb938d7cc86fd7d7baf16c6fc9592a79e4e110/src/WebJobs.Script.WebHost/StartupContextProvider.cs#L143
https://github.com/Azure/azure-functions-host/blob/e5bb938d7cc86fd7d7baf16c6fc9592a79e4e110/src/WebJobs.Script.WebHost/Management/AtlasInstanceManager.cs#L86
Contributor guide
Research direction
Start with the linked sections in StartupContextProvider.cs and Management/AtlasInstanceManager.cs, then trace how admin/instance/assign reaches those serialization calls. Measure the endpoint's cold-start path before and after the change; done means the identified serialization uses source-generated STJ metadata without changing endpoint behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp
- Domain
- api, backend, performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100