Update
This commit is contained in:
parent
2efc415ac4
commit
70c10acfc5
61 changed files with 1970 additions and 1954 deletions
|
@ -6,7 +6,7 @@ It is believed and sometimes relied on that P != NP (in which case P would be a
|
|||
|
||||
## Explanation
|
||||
|
||||
In the context of [computational complexity](computational_complexity.md) of algorithms we talk about different types of algorithm time complexities, i.e. different "speeds" of algorithms. This "speed" doesn't mean actual running time of the algorithm in real life but rather how quickly the running time grows depending on the amount of input data to it (so rather something akin "[scalability](scalability.md)"), i.e. we are interested only in the shape of the function that describes how the amount of input data affects the running time of the algorithm. The types of time complexity are named after mathematical functions that grow as quickly as this dependence, so we have a *constant* time complexity, *logarithmic* time complexity, *linear* time complexity etc.
|
||||
In the context of [computational complexity](computational_complexity.md) of algorithms we talk about different types of algorithm time complexities, i.e. different "speeds" of algorithms. This "speed" doesn't mean actual running time of the algorithm in real life but rather how quickly the running time grows depending on the amount of input data to it (so rather something akin to "[scalability](scalability.md)"), i.e. we are interested only in the shape of the function that describes how the amount of input data affects the running time of the algorithm. The types of time complexity are named after mathematical functions that grow as quickly as this dependence, so we have a *constant* time complexity, *logarithmic* time complexity, *linear* time complexity etc.
|
||||
|
||||
Then we have classes of computational problems. The classes divide problems based on how "fast" they can be solved.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue