nnethercote/perf-book

Issues

• Document `iter().copied()` vs `iter()` for small data types

  #83 opened 5 months ago by Dan-wanna-M
  1

• Update #[inline] documentation

  #84 opened 5 months ago by ppershing
  3

• `test_and_maybe_deploy` use `actions` that use `deprecated` version of `Node.js`

  #81 opened 7 months ago by hamirmahal
  3

• Different linker project-wise

  #79 opened 7 months ago by frederikhors
  1

• Async optimizations

  #45 opened 2 years ago by insanitybit
  1

• Question about CPU Specific Instructions, could it work with cross compile?

  #78 opened 9 months ago by asuper0
  2

• Add Intel Vtune as another option for Profiling

  #74 opened a year ago by stevenhuyn
  4

• I/O: `Read::bytes()` is very slow, even on a `BufReader`

  #69 opened a year ago by Shnatsel
  6

• Document external `.next()` vs internal `.try_fold()` iteration

  #70 opened a year ago by Shnatsel
  0

• I/O: `.lines()` iterator is slower than a manual loop over `.read_line()` due to allocations

  #68 opened a year ago by Shnatsel
  5

• "Machine code" section should suggest `cargo asm`

  #64 opened a year ago by Shnatsel
  4

• Mention Intel VTune Profiler

  #63 opened a year ago by Gabaa
  1

• Inlining: mention `missing_inline_in_public_items` Clippy lint

  #65 opened a year ago by Shnatsel
  1

• Iterators: recommend interior iteration - `iter.for_each()` instead of `for x in iter`

  #51 opened a year ago by Shnatsel
  4

• Inlining: mention that it is not transitive

  #66 opened a year ago by Shnatsel
  1

• Outdated mention of `tikv-jemallocator`

  #67 opened a year ago by Boshen
  3

• Publish ePUB

  #58 opened 2 years ago by mcandre
  7

• Static vs Dynamic Dispatch

  #44 opened 2 years ago by insanitybit
  1

• Expand chapter on LLVM IR

  #60 opened 2 years ago by Boshen
  2

• Inlining - None

  #61 opened 2 years ago by Lokathor
  1

• mention hashbrown, faster HashMap implementation

  #59 opened 2 years ago by mokurin000
  1

• Add a link to the samply profiler

  #56 opened 2 years ago by djc
  1

• Iterators: recommend the `chunks_exact` + `remainder` pattern

  #52 opened 2 years ago by Shnatsel
  1

• Collections: accessing `&mut [T]` is faster than `Vec<T>`

  #50 opened 2 years ago by Shnatsel
  9

• Arrays index out of bounds checking in rust

  #54 opened 2 years ago by skibon02
  10

• Benchmarking: mention that both input and output need to be in a `black_box()`

  #53 opened 2 years ago by Shnatsel
  3

• My question and doubt about "using CPU specific instructions"

  #55 opened 2 years ago by SatinWukerORIG
  1

• Add a note about checking for CPU Compatibility for target-cpu=native

  #43 opened 2 years ago by joshuataylor
  2

• Possibly add `tinyset` to hashing-section

  #42 opened 3 years ago by Glitchy-Tozier
  2

• Mention nohash_hasher

  #41 opened 3 years ago by Glitchy-Tozier
  3

• Add Instrument profiler for Mac

  #39 opened 3 years ago by yvgny
  1

• Should bytehound be included in the list of profilers?

  #37 opened 3 years ago by saethlin
  1

• LLD usage

  #34 opened 4 years ago by pravic
  1

• ‘Compile Times’ should be 'Compile Time'

  #32 opened 4 years ago by mokurin000
  1

• Profiler for Windows

  #31 opened 4 years ago by d00z3l
  3

• Discuss Iterator trait implications for allocations?

  #28 opened 4 years ago by djc
  3

• Consider talking about platform support for tooling

  #27 opened 4 years ago by djc
  1

• Mention the bencher crate

  #26 opened 4 years ago by djc
  1

• `Rc::make_mut()` also applies to `Arc::make_mut()`

  #29 opened 4 years ago by djc
  1

• Chapter 8: mention fxhash support

  #24 opened 4 years ago by tylervipond
  2

• Define "hot"

  #21 opened 4 years ago by sburris0
  3

• What are the downsides of the `Cow` type?

  #12 opened 4 years ago by seanchen1991
  2

• Mention cranelift to reduce compile time?

  #15 opened 4 years ago by FilipAndersson245
  1

• Floating point

  #11 opened 4 years ago by jedbrown
  3

• Some more topic ideas

  #4 opened 4 years ago by najamelan
  1

• Maybe it's worth mentioning coz

  #3 opened 4 years ago by najamelan
  1

• Memory profiling: heaptrack

  #7 opened 4 years ago by luben
  1

• Implication that only Intel CPUs support AES instructions

  #13 opened 4 years ago by redzic
  1

• A little more on Parallelization

  #9 opened 4 years ago by lukesdm
  1