Lines Matching refs:zstd

30 Zstd uses a branch-based workflow for making changes to the codebase. Typically, zstd
37         * Checkout your fork of zstd if you have not already
39         git checkout https://github.com/<username>/zstd
40         cd zstd
44         git pull https://github.com/facebook/zstd dev
99 …* Eventually, someone from the zstd team will approve your pull request and not long after merge i…
106 …     that the change must make it to an official zstd release for it to be meaningful. We recommend
108 …  their change makes it to the next release of zstd. Users will often discover bugs in your code or
144 Performance is extremely important for zstd and we only merge pull requests whose performance
223 be enabled by default when building zstd.
233 The fastest signal you can get regarding your performance changes is via the in-build zstd cli
239 For example: say you have made a change that you believe improves the speed of zstd level 1. The
241 is `zstd -b`. You might try to do something like this. Note: you can use the `-i` option to
247 $ make && cp zstd zstd-old
249 $ make && cp zstd zstd-new
250 $ zstd-old -i5 -b1 <your-test-data>
252 $ zstd-new -i5 -b1 <your-test-data>
299 $ zstd -b1 -i5 <my-data> # this will run for 5 seconds
305     `zstd`
313     zstd and your benchmarking scripg using debug flags. On mac and linux, this just means
350 is to configure your personal fork of zstd with each of the CI platforms. Below, you'll find
354 Follow these steps to link travis-ci with your github fork of zstd
361 6. Select 'Only select repositories' and select your fork of zstd from the drop down
371 Follow these steps to link circle-ci with your girhub fork of zstd
378 …h repositories you want to give appveyor permission to. Select your fork of zstd if you're prompted
390 branch of zstd. You can then find the status of the tests on the PR's page. You can also