Cold Start
Cold Start
A phenomenon where a program that hasn't run in a while takes longer than usual to start up.
In Simple Terms
Cold start is when a server or program that hasn't been used in a while takes noticeably longer than usual to get up and running. For example, if you try to run a program on a cloud service that nobody has accessed for some time, the server first needs to spin up and get ready. Because of that setup work, only the very first request ends up responding slowly.
Behind the Name
Cold start combines the English words "cold" and "start." It comes from starting up machinery, like a car engine, from a completely cold state. In the IT world, it describes getting a server or program running again from that same cold, unprepared state after it's been sitting idle for a while.
Take a Closer Look!
Cold start refers to the phenomenon where the very first launch of a program or server that hasn't been running for a while takes extra time.
Cloud services keep costs down by temporarily shutting down unused programs and fully releasing system resources like memory and CPU. So when a request comes in after a long gap, the whole setup process has to be rebuilt from scratch: loading the program, spinning up a virtual environment (like a container) to run it in, and allocating memory. That startup overhead is what makes the first response slow.
By contrast, starting up from a state that's already prepared and ready to go instantly is called a "warm start." A warm start runs in an instant, but keeping things in that ready state means the program has to stay running all the time, which costs money. Cold start is a key factor to weigh when balancing cost savings against a system's ability to respond quickly.