|
|
@@ -24,7 +24,7 @@ chunks and write_to work the same.
|
|
|
|
|
|
https://poby.medium.com/memory-profiling-using-valgrind-b30514f35117
|
|
|
|
|
|
-```valgrind --log-file=memory1.log target/release/go-up update```
|
|
|
+`valgrind --log-file=memory1.log target/release/go-up update`
|
|
|
|
|
|
No leaks. As if... ;)
|
|
|
|
|
|
@@ -38,7 +38,7 @@ massif-visualizer massif.out.2496324
|
|
|
## Valgrind memory usage
|
|
|
|
|
|
Logging total memory usage:
|
|
|
-```cargo build --release; valgrind --log-file=memory1.log target/release/go-up update```
|
|
|
+`cargo build --release; valgrind --log-file=memory1.log target/release/go-up update`
|
|
|
|
|
|
```
|
|
|
==2470578== HEAP SUMMARY:
|
|
|
@@ -50,6 +50,7 @@ Logging total memory usage:
|
|
|
I was concerned about the total bytes allocated, but that's not all at one time.
|
|
|
|
|
|
Example run:
|
|
|
+
|
|
|
```
|
|
|
thor@mount-olympus:~/Development/rust/reqwest/go-up$ cargo run -- update
|
|
|
Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.07s
|
