Skip to content

Commit

Permalink
Add a missing 'to'.
Browse files Browse the repository at this point in the history
  • Loading branch information
Frank Shearar committed Sep 23, 2013
1 parent 5654b77 commit b31e60e
Show file tree
Hide file tree
Showing 4 changed files with 4 additions and 4 deletions.
2 changes: 1 addition & 1 deletion input/1_intro.md
Original file line number Diff line number Diff line change
Expand Up @@ -61,7 +61,7 @@ Depending on the context, this may involve achieving one or more of the followin
- High throughput (rate of processing work)
- Low utilization of computing resource(s)

There are tradeoffs involved in optimizing for any of these outcomes. For example, a system may achieve a higher throughput by processing larger batches of work thereby reducing operation overhead. The tradeoff would be longer response times for individual pieces of work due batching.
There are tradeoffs involved in optimizing for any of these outcomes. For example, a system may achieve a higher throughput by processing larger batches of work thereby reducing operation overhead. The tradeoff would be longer response times for individual pieces of work due to batching.

I find that low latency - achieving a short response time - is the most interesting aspect of performance, because it has a strong connection with physical (rather than financial) limitations. It is harder to address latency using financial resources than the other aspects of performance.

Expand Down
2 changes: 1 addition & 1 deletion output/ebook.html
Original file line number Diff line number Diff line change
Expand Up @@ -133,7 +133,7 @@ <h3>Performance (and latency)</h3>
<li>High throughput (rate of processing work)</li>
<li>Low utilization of computing resource(s)</li>
</ul>
<p>There are tradeoffs involved in optimizing for any of these outcomes. For example, a system may achieve a higher throughput by processing larger batches of work thereby reducing operation overhead. The tradeoff would be longer response times for individual pieces of work due batching.</p>
<p>There are tradeoffs involved in optimizing for any of these outcomes. For example, a system may achieve a higher throughput by processing larger batches of work thereby reducing operation overhead. The tradeoff would be longer response times for individual pieces of work due to batching.</p>
<p>I find that low latency - achieving a short response time - is the most interesting aspect of performance, because it has a strong connection with physical (rather than financial) limitations. It is harder to address latency using financial resources than the other aspects of performance.</p>
<p>There are a lot of really specific definitions for latency, but I really like the idea that the etymology of the word evokes:</p>
<dl>
Expand Down
2 changes: 1 addition & 1 deletion output/intro.html
Original file line number Diff line number Diff line change
Expand Up @@ -106,7 +106,7 @@ <h3>Performance (and latency)</h3>
<li>High throughput (rate of processing work)</li>
<li>Low utilization of computing resource(s)</li>
</ul>
<p>There are tradeoffs involved in optimizing for any of these outcomes. For example, a system may achieve a higher throughput by processing larger batches of work thereby reducing operation overhead. The tradeoff would be longer response times for individual pieces of work due batching.</p>
<p>There are tradeoffs involved in optimizing for any of these outcomes. For example, a system may achieve a higher throughput by processing larger batches of work thereby reducing operation overhead. The tradeoff would be longer response times for individual pieces of work due to batching.</p>
<p>I find that low latency - achieving a short response time - is the most interesting aspect of performance, because it has a strong connection with physical (rather than financial) limitations. It is harder to address latency using financial resources than the other aspects of performance.</p>
<p>There are a lot of really specific definitions for latency, but I really like the idea that the etymology of the word evokes:</p>
<dl>
Expand Down
2 changes: 1 addition & 1 deletion output/single-page.html
Original file line number Diff line number Diff line change
Expand Up @@ -156,7 +156,7 @@ <h3>Performance (and latency)</h3>
<li>High throughput (rate of processing work)</li>
<li>Low utilization of computing resource(s)</li>
</ul>
<p>There are tradeoffs involved in optimizing for any of these outcomes. For example, a system may achieve a higher throughput by processing larger batches of work thereby reducing operation overhead. The tradeoff would be longer response times for individual pieces of work due batching.</p>
<p>There are tradeoffs involved in optimizing for any of these outcomes. For example, a system may achieve a higher throughput by processing larger batches of work thereby reducing operation overhead. The tradeoff would be longer response times for individual pieces of work due to batching.</p>
<p>I find that low latency - achieving a short response time - is the most interesting aspect of performance, because it has a strong connection with physical (rather than financial) limitations. It is harder to address latency using financial resources than the other aspects of performance.</p>
<p>There are a lot of really specific definitions for latency, but I really like the idea that the etymology of the word evokes:</p>
<dl>
Expand Down

0 comments on commit b31e60e

Please sign in to comment.