Gross over-simplification of web page timing

[tbenbrahim]

"If it takes a second to make a page, that’s still too slow—there are only 2.6 million seconds in a month. So you need to figure out how to serve about 10 pages per second. "
Point 1: A second to make a page is too slow for usability and user retention reasons, but not for the timing reasons outlined in the articles. During most of that second, the thread "making" the page is blocked (and sleeping) waiting on database I/O, file I/O, etc..., allowing other threads to do work. You could have a hundred threads each taking one second to make a page, as long as the CPU time consumed by each thread is less than 10ms, you would be fine (and on a 4 core hyper-threaded CPU, that time constraint climbs to less than 80ms of CPU time, an eternity in computer time. in fact with a good database, good file I/O and ample memory for caching, 80ms should accommodate both CPU time and User time, i.e. total clock time, for the majority of requests).
Point 2: You should be able to serve 10 concurrent pages a second on a $300 Atom powered computer from Walmart. If not, you need to seriously look at your code and choice of technology.