Cold start (computing): Difference between revisions
No edit summary |
m Fixed grammar |
||
| Line 1: | Line 1: | ||
'''Cold start''' in [[computing]] refers to a problem where a system or its part was created or restarted and is not working at its normal operation. The problem can be related to initialising internal [[Object (computer science)|objects]] or populating [[Cache (computing)|cache]] or starting up subsystems. |
'''Cold start''' in [[computing]] refers to a problem where a system or its part was created or restarted and is not working at its normal operation. The problem can be related to initialising internal [[Object (computer science)|objects]] or populating [[Cache (computing)|cache]] or starting up subsystems. |
||
In a typical [[web service]] |
In a typical [[web service]] system the problem occurs after restarting the server and also when clearing cache (e.g. after releasing new version). First requests to the web service will cause significantly more load due to server cache being populated and due to [[Web browser|browser]] [[Web cache|cache]] being cleared and new resources requested. Other services like a [[caching proxy]] or [[web accelerator]] will also need time to gather new resources and operate normally. |
||
Similar problem occurs when creating instances in a hosted environment and instances in [[cloud computing]] services<ref>{{Cite web|url=https://mikhail.io/serverless/coldstarts/aws/|title=Cold Starts in AWS Lambda|website=mikhail.io|language=en-us|access-date=2020-01-31}}</ref>. |
Similar problem occurs when creating instances in a hosted environment and instances in [[cloud computing]] services<ref>{{Cite web|url=https://mikhail.io/serverless/coldstarts/aws/|title=Cold Starts in AWS Lambda|website=mikhail.io|language=en-us|access-date=2020-01-31}}</ref>. |
||
Revision as of 10:38, 20 September 2020
Cold start in computing refers to a problem where a system or its part was created or restarted and is not working at its normal operation. The problem can be related to initialising internal objects or populating cache or starting up subsystems.
In a typical web service system the problem occurs after restarting the server and also when clearing cache (e.g. after releasing new version). First requests to the web service will cause significantly more load due to server cache being populated and due to browser cache being cleared and new resources requested. Other services like a caching proxy or web accelerator will also need time to gather new resources and operate normally.
Similar problem occurs when creating instances in a hosted environment and instances in cloud computing services[1].
Cold start (or cold boot) may also refer to a booting process of a single computer (or virtual machine)[2]. In this case services and other startup applications are executed after reboot. System is typically made available to the user even though startup operations are still performed and slow down other operations.
Another type of problem is when the data model of a particular system requires connections between objects. In that case new objects will not operate normally until those connections are made. This is well known problem with recommender systems[3][4].
See also
References
- ^ "Cold Starts in AWS Lambda". mikhail.io. Retrieved 2020-01-31.
- ^ "What is Cold Boot? - Definition from Techopedia". Techopedia.com. Retrieved 2020-01-31.
- ^ Bobadilla, Jesús; Ortega, Fernando; Hernando, Antonio; Bernal, Jesús (February 2012). "A collaborative filtering approach to mitigate the new user cold start problem". Knowledge-Based Systems. 26: 225–238. doi:10.1016/j.knosys.2011.07.021.
- ^ Lika, Blerina; Kolomvatsos, Kostas; Hadjiefthymiades, Stathes (March 2014). "Facing the cold start problem in recommender systems". Expert Systems with Applications. 41 (4): 2065–2073. doi:10.1016/j.eswa.2013.09.005.