4 ms·
If you take slides 52[1] to 63[2], you can see the emphasis put into run-time diagnosis. Which is really important for largely distributed systems. Google wrot
by DanielRibeiro 14y ago
If you take slides 52[1] to 63[2], you can see the emphasis put into run-time diagnosis.
Which is really important for largely distributed systems. Google wrote a little about it when they introduced their global run-time performance tracing tool called Dapper[3] in "Dapper, a Large-Scale Distributed Systems Tracing Infrastructure"[4]"
Modern Internet services are often implemented as complex, large-scale distributed systems. These applications are constructed from collections of software modules that may be developed by different teams, perhaps in different programming languages, and could span many thousands of machines across multiple physical facili- ties. Tools that aid in understanding system behavior and reasoning about performance issues are invaluable in such an environment.
[1] http://monkey.org/~marius/talks/twittersystems/#52 http://monkey.org/~marius/talks/twittersystems/#52
[2] http://monkey.org/~marius/talks/twittersystems/#63 http://monkey.org/~marius/talks/twittersystems/#63
[3] http://highscalability.com/blog/2010/4/27/paper-dapper-googles-large-scale-distributed-systems-tracing.html http://highscalability.com/blog/2010/4/27/paper-dapper-googl...
[4] http://research.google.com/pubs/pub36356.html http://research.google.com/pubs/pub36356.html
- zxypoo 14y agoTwitter open sourced Zipkin, their distributed tracing system based on the Dapper paper: http://twitter.github.com/zipkin/ http://twitter.github.com/zipkin/