Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion introduction/performance.rst
Original file line number Diff line number Diff line change
Expand Up @@ -314,7 +314,7 @@ much bandwidth they need. Video applications are a prime
example. Suppose one wants to stream a video to a small screen that
has a resolution of 352 by 240 pixels. If each pixel is represented by
24 bits of information, as would be the case for 24-bit color, then
the size of each frame would be (352 × 240 × 24) / 8 = 247.5 KB. If
the size of each frame would be (352 × 240 × 24) / (8 × 1024) = 247.5 KB. If
the application needs to support a frame rate of 30 frames per second,
then it might request a throughput rate of 60.8 Mbps. The ability of the
network to provide more bandwidth is of no interest to such an
Expand Down
4 changes: 2 additions & 2 deletions introduction/requirements.rst
Original file line number Diff line number Diff line change
Expand Up @@ -96,8 +96,8 @@ requirement in Section |Intro|.4.

The fourth requirement is that the network be *high-performance.*
Everyone wants the network to be fast, but performance is
multifaceted. Some applications care about response time; how long
it takes to send and receive a message. Others care about throughput;
multifaceted. Some applications care about response time: how long
it takes to send and receive a message. Others care about throughput:
how long it takes to download a large file. Still others care that
packet delivery is predictable, so that a video stream plays without
jarring pauses. All of these metrics depend on physical limitations,
Expand Down
Loading