Signed-off-by: SeongJae Park <sj38.park@xxxxxxxxx>
---
debugging/debugging.tex | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/debugging/debugging.tex b/debugging/debugging.tex
index 0162442..2207a0e 100644
--- a/debugging/debugging.tex
+++ b/debugging/debugging.tex
@@ -1694,7 +1694,7 @@ much a bug as is incorrectness.
And in this case, any performance bug that prevents the model from
running faster than the actual weather prevents any forecasting.
Given that the whole purpose of purchasing the large clustered
- supercomputer was to forecast weather, if you cannot run the
+ supercomputers was to forecast weather, if you cannot run the
model faster than the weather, you would be better off not running
the model at all.
@@ -1766,7 +1766,7 @@ Unfortunately, it is often impractical for the following reasons:
\item The application might be proprietary, and you
might not have the right to run the intended application.
\item The application might require more hardware
- that you have access to.
+ than you have access to.
\item The application might use data that you cannot legally
access, for example, due to privacy regulations.
\end{enumerate}
@@ -1791,7 +1791,7 @@ on the cache misses that were actually responsible for the majority
of the problem~\cite{McKenney93}.
An old-school but quite effective method of tracking down performance
-and scalability bugs is to run your programmer under a debugger,
+and scalability bugs is to run your program under a debugger,
then periodically interrupt it, recording the stacks of all threads
at each interruption.
The theory here is that if something is slowing down your program,
--
1.9.1
--
To unsubscribe from this list: send the line "unsubscribe perfbook" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
