chapter 1 section 5 edits. mostly reductions. #68
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I will not fight in this case. But in general, I don't mind repeating things as long as it makes my point clear. Yes, some people are very good at reading between the lines. But not all. If they already understand what they're reading, they will easily swallow that sentence, I don't see a problem here. Again, I'm not talking about this particular case. In this case, I agree with your changes. I rather wanted to share my way of thinking. |
dendibakh
reviewed
Sep 7, 2024
|
|
||
| Examples provided in this book are primarily based on open-source software: Linux as the operating system, the LLVM-based Clang compiler for C and C++ languages, and various open-source applications and benchmarks[^1] that you can build and run. The reason is not only the popularity of these projects but also the fact that their source code is open, which enables us to better understand the underlying mechanism of how they work. This is especially useful for learning the concepts presented in this book. This doesn't mean that we will never showcase proprietary tools. For example, we extensively use Intel® VTune™ Profiler. | ||
| Examples provided in this book are primarily based on open source software: Linux as the operating system, the LLVM-based Clang compiler for C and C++ languages, and various open source applications and benchmarks[^1] that you can build and run. The reason is not only the popularity of these projects but also the fact that their source code is open, which enables us to better understand the underlying mechanism of how they work. This is especially useful for learning the concepts presented in this book. This doesn't mean that we will never showcase proprietary tools. For example, we extensively use Intel® VTune™ Profiler. |
| * Our customers complain about the slowness of my application, where should I start? | ||
| * Why my hand-written compression algorithm performs two times slower than the conventional one? | ||
| * Our customers complain about the slowness of my application. How should I investigate? | ||
| * Why does my bespoke compression algorithm perform slower than the conventional one? |
There was a problem hiding this comment.
[Denis]: change back to handwritten
| * Chapter 6 examines features provided by modern Intel, AMD, and ARM-based CPUs to support and enhance performance analysis. It shows how they work and what problems they help to solve. | ||
| * Chapter 7 gives an overview of the most popular tools available on major platforms, including Linux, Windows, and MacOS, running on x86- and ARM-based processors. | ||
| * Chapter 5 explores the most popular performance analysis approaches. We describe how profiling tools work and what sort of data they can collect. | ||
| * Chapter 6 examines features provided by modern Intel, AMD, and ARM CPUs to support and enhance performance analysis. It shows how they work and what problems they help to solve. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It's "handwritten", not "hand-written". Hyphenation rules are complex and maddening. Sorry, man; I didn't do it.
Did you mean "my algorithm" or "my implementation of the algorithm"? It seemed like the first, hence "bespoke" rather than "handwritten" in the end anyway.
No "here is an outline of the book chapters". Just give the outline. People know what an outline looks like.
It's "open source", not "open-source". Mwahahahaha kill me.
Eliminate "* Chapter 1 is an introduction that you're reading right now.". https://stuff.mit.edu/people/dpolicar/writing/prose/text/titleOfTheStory.html