update README
This commit is contained in:
parent
574541d47f
commit
1b3112b6c8
|
@ -19,6 +19,8 @@ Questions
|
||||||
4. Our support team suggests that an average response time > 2 seconds is much too slow. How would you write a program that read the output file and printed "HOST <host> IS TOO SLOW AT <TIMESTAMP>." if the last 5, 1 minute summaries for a host were greater than 2 seconds?
|
4. Our support team suggests that an average response time > 2 seconds is much too slow. How would you write a program that read the output file and printed "HOST <host> IS TOO SLOW AT <TIMESTAMP>." if the last 5, 1 minute summaries for a host were greater than 2 seconds?
|
||||||
5. In the real world, we don’t have guarantees about clock monotonicity, and we see data arrive late_ . That is to say that there is no hard guarantee that, for L_ =request log line number and T_=the timestamp, T.sub(L-1)_ is chronologically less than T.sub(L)_. Describe a way in which your program could handle request logs that arrive up to N minutes late. What is the impact on memory usage, and “downstream” services such as the “SLOW RESPONSE TIME” program discussed above?
|
5. In the real world, we don’t have guarantees about clock monotonicity, and we see data arrive late_ . That is to say that there is no hard guarantee that, for L_ =request log line number and T_=the timestamp, T.sub(L-1)_ is chronologically less than T.sub(L)_. Describe a way in which your program could handle request logs that arrive up to N minutes late. What is the impact on memory usage, and “downstream” services such as the “SLOW RESPONSE TIME” program discussed above?
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
Answers
|
Answers
|
||||||
-------
|
-------
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue