|
|
@@ -1,3 +1,14 @@
|
|
|
+# TO DO
|
|
|
+
|
|
|
+* Have a good place for the cache directory.
|
|
|
+* Expire entries in the cache.
|
|
|
+* Possibly add my own anyhow "context", so when there's a permission issue, the user knows where to look.
|
|
|
+
|
|
|
+# So Far...
|
|
|
+
|
|
|
+* Fixes the GOROOT and GOPATH for files and directories with a+r only attributes.
|
|
|
+* tar strips off the "go" directory within the archive.
|
|
|
+
|
|
|
# Go
|
|
|
|
|
|
Ok, it looks like GOROOT is managed by go. See `go env`.
|
|
|
@@ -15,7 +26,9 @@ https://poby.medium.com/memory-profiling-using-valgrind-b30514f35117
|
|
|
|
|
|
```valgrind --log-file=memory1.log target/release/go-up update```
|
|
|
|
|
|
-No leaks. ;)
|
|
|
+No leaks. As if... ;)
|
|
|
+
|
|
|
+## Viewing peak heap memory usage:
|
|
|
|
|
|
```
|
|
|
valgrind --tool=massif --stacks=yes --log-file=valgrind3.log target/release/go-up update
|
|
|
@@ -33,6 +46,9 @@ Logging total memory usage:
|
|
|
==2470578== total heap usage: 217,384 allocs, 211,526 frees, 269,243,726 bytes allocated
|
|
|
==2470578==
|
|
|
```
|
|
|
+
|
|
|
+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
|
