| go test -run=. -bench=. -benchtime=5s -count 5 -benchmem -cpuprofile=cpu.out -memprofile=mem.out -trace=trace.out ./package | tee bench.txt | |
| go tool pprof -http :8080 cpu.out | |
| go tool pprof -http :8081 mem.out | |
| go tool trace trace.out | |
| go tool pprof $FILENAME.test cpu.out | |
| # (pprof) list <func name> | |
| # go get -u golang.org/x/perf/cmd/benchstat | |
| benchstat bench.txt |
| package main | |
| import ( | |
| "fmt" | |
| "testing" | |
| ) | |
| type SampleStruct struct { | |
| a int | |
| b int |
08/16/17 by Sergey Grebenshchikov
This is a quick tutorial on how to test code using the GoMock mocking library and the standard library testing package testing.
GoMock is a mock framework for Go. It enjoys a somewhat official status as part of the github.com/golang organization, integrates well with the built-in testing package, and provides a flexible expectation API.
| // Must install ImageMagick first | |
| http://www.imagemagick.org/script/index.php | |
| //This compresses a jpg with no visible loss of quality. Add in your own file names for target.jpg and result.jpg | |
| convert -strip -interlace Plane -sampling-factor 4:2:0 -quality 85% target.jpg result.jpg | |
| // This does the same as above but to an entire folder (will overwrite original files): | |
| mogrify -strip -interlace Plane -sampling-factor 4:2:0 -quality 85% *.jpg | |
| //This does the same thing but to all subfolders as well (Be careful with this one it will overwrite all original files) |
| #!/bin/bash | |
| # | |
| # Docker Daemon varsayilan olarak ag iletisimi olmadan | |
| # sadece Unix socket uzerinden calismaktadir. | |
| # Docker Client ve Daemon arasinda HTTPS uzerinden | |
| # guvenli iletisimin kurulmasi icin TLS aktif hale getirilmelidir. | |
| # Client ve Server/daemon arasindaki guvenli iletisim agi | |
| # icin gereken client ve server sertifikasyonlarini | |
| # olusturmaliyiz. | |
| # |
| go test -run=. -bench=. -benchtime=5s -count 5 -benchmem -cpuprofile=cpu.out -memprofile=mem.out -trace=trace.out ./package | tee bench.txt | |
| go tool pprof -http :8080 cpu.out | |
| go tool pprof -http :8081 mem.out | |
| go tool trace trace.out | |
| go tool pprof $FILENAME.test cpu.out | |
| # (pprof) list <func name> | |
| # go get -u golang.org/x/perf/cmd/benchstat | |
| benchstat bench.txt |
| # Stop all containers | |
| docker stop `docker ps -qa` | |
| # Remove all containers | |
| docker rm `docker ps -qa` | |
| # Remove all images | |
| docker rmi -f `docker images -qa ` | |
| # Remove all volumes |
Этот текст о том, с чего начать прежде чем писать в https://telegram.me/prophp7
Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.
In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.
Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j
