3 ms·
It was just an example, not necessarily a realistic one. The point is that we want to compare how quickly a processor will compute our problem, not how many ins
by fluoridation 3y ago
It was just an example, not necessarily a realistic one. The point is that we want to compare how quickly a processor will compute our problem, not how many instructions it's going to execute. If it was a car you want to compare things like its top speed and acceleration, not something inane like engine revolutions per kilometer. You measure and compare things that are relevant to the user, not implementation details.
- dragontamer 3y agoOkay, I think I see what you're saying now. I misinterpreted your statements earlier.
- magicalhippo 3y ago> not something inane like engine revolutions per kilometer Unrelated to the thread but I just read that Top Fuel dragster engines only do about 240 revolutions over the 1000 foot race[1]. Never thought of it like that before so blew my mind a little. [1]: https://en.wikipedia.org/wiki/Top_Fuel#Performance https://en.wikipedia.org/wiki/Top_Fuel#Performance