Skip to content

Fast startup and slow first request vs slow startup and fast first request #62578

Open
@andrew-vdb

Description

@andrew-vdb

Summary

While we want to have the best of both world. I believe we need to make a switch which way the application published.

Motivation and goals

I'm building desktop app with spa, blazor, min api and run it with chrome. Startup taking sometimes like 5 seconds. Making it aot give no difference. In this case i want to have very fast startup.

I'm also building web application, same stack but hosted in azure app service. I dont mind for slow start up here but i really want to have very fast first request. I tried by making warm up request, does not seems to work.

The goal is to have switch in publish profile which performance level we want to have.

In scope

Startup and first request performance.

Out of scope

Risks / unknowns

Examples

Metadata

Metadata

Assignees

No one assigned

    Labels

    NativeAOTarea-networkingIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractionsdesign-proposalThis issue represents a design proposal for a different issue, linked in the description

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions