Skip to main content

Browse the archive

Revision 6ce32902720bacfc81cf7fd94fe95c927bb29daf authored by Diana Savatina on 22 March 2024, 15:51:59 UTC, committed by Diana Savatina on 27 March 2024, 14:16:04 UTC 
profiler: TXT and/or JSON configurable
 
    - txt, json or both can be selected for output
    - json output contains readiable timestamps
    - max range is configurable to be used for aggregated data

Example:
export PROFILING=yes:txt_and_json:1000:$HOME/Documents/features/reduce_blocktime/local

{ "aggregated": [],
    "recorded":
    [ { "name": "initialization",
        "start": { "wall": "2024-03-20T15:42:38.623-00:00", "cpu": 0.289436 },
        "duration": { "wall": 0.0199749, "cpu": 0.009858 },

> dune exec src/lib_base/unix/test/main.exe --
    --file test_simple_profiler.ml

TEST: test_parse_profiling_config

                config : {} my_dir
            expected : {no_lod}
                empty : {no_lod}

                config : {YES:txt:999:/my/path/here} my_dir
            expected : {terse txt 999 /my/path/here}
                full : {terse txt 999 /my/path/here}
1 parent 04e5744
Raw File
contributing.md 
# Contributing

Thank you for considering contributing to Tezos. This is a large codebase and
due to the on-chain governance nature of Tezos we use some non-standard
workflows.

There are two classes of changes and both are treated differently:
* Changes to the shell implementation
* Changes to the protocol implementation

## Shell Implementation
The shell is not part of the consensus state machine and hence every full node
can have a different/custom version of the shell while still running the same
protocol. A good example is how Ethereum has Parity and Geth, both are different
shells but they are running the same protocol.

Making changes to the shell is straightforward. Fork this repo, and then branch
from `master`. Once you have made your changes please submit a merge request on
gitlab against the `master` branch.

## Protocol Implementation
The protocol is the Tezos state machine and run in consensus. It is fully
deterministic and every node in the network has to arrive at the same output
given the same input.

Making changes to the protocol is slightly different than one would expect. You
branch from the latest `master` branch, make changes to the protocol, and then
push them to your own branch in your fork. Please start from `proto_alpha`, and
then follow the naming convention of `proto_00*_***` by renaming the former
folder. You may create a merge request against the `master` branch, but it will
get merged only once the network has voted on your proposal and accepted it.
After it has gone through the Tezos governance process it will also get merged
into `zeronet` for testing and finally into `mainnet` for deployment.

[Here](http://tezos.gitlab.io/developer/contributing.html) you can
find more documentation on the development flow and [here](http://tezos.gitlab.io/whitedoc/voting.html)
you can find more information on the governance and voting process.

## Conclusion
Hacking on Tezos is awesome and everyone is welcome. If you discover
inconsistencies in this document please fix them to make it easier for the next
person. Furthermore, please don't hesitate to ask questions, we don't bite.

## Further
To get more details on the contribution process, check out the
[online contributing guidelines](http://tezos.gitlab.io/developer/contributing.html).
back to top