Benchmarking mastercomfig wiki

* ## ***The author is not mastercoms but one of the config users***






### My vision
Hello. I think that making one place to post all the benchmarks related to mastercomfig and to TF2 code in general is better than posting those benchmarks randomly in the one of the currently 32 pages in the TF.TV thread on mastercomfig, and that's why I  decided to make this page. results that were got using only one config / set of commands using mastercomfig here won't help, since there won't be anything to compare to. I also don't think that comparing mastercomfig to other configs shouldn't take place here, since it won't help the users of ***this*** config. I think that this page should be dedicated to testing how specific commands and sets of commands affect TF2's performance.

# Benchmarking

## How to benchmark a demo
 * Download [this demo](https://mega.nz/#!f8tlhDhR!nYgghqybOK15ObUykEczewB3242XHb_bJ4JP0rv1q6k):
 * Extract it to `Steam/SteamApps/common/Team Fortress 2/tf`
 * Launch TF2 and make sure no resource heavy processes are running
 * Enter the first set of commands that you want to test
 * Type in console `timedemo benchmark_test`
 * You'll get a result that will look like that: `X frames X seconds X fps ( X ms/f) X fps variability` just that all the
 X's will be numbers. Be sure to write this result down.
 * Enter the second set of commands that you want to test and repeat

**While benchmarking a demo, notice:**
* Be sure that all demos are the same demos.
* Please benchmark using other demos than the one above only if it's necessary. For example, if you want to test the
effects of the command/s on a specific map that has a special prop or something else.
* **Be sure that the background processes while running all of the benchmarks are as minor and as equal as you can, or else the results won't be accurate.**
* **Be sure to enter the commands that you want to test and to change them before benchmarking each time**
* **Be sure that expect for the commands that you are testing, all commands stay the same during all benchmarks**








# How to Post Benchmarks

## How to make a documentation of the benchmarks

* **Firstly, create a [new gist](https://gist.github.com/).**
  **In it, include the following information:**
* The command/commands you're testing. for example:
```
1. mat_phong 1, r_rimlight 1, net_graph 5
2. mat_phong 0, r_rimlight 1, net_graph 0
3. mat_phong 0, r_rimlight 0, net_graph 2
4. mat_phong 1, r_rimlight 0, net_graph 1
```

If a command is mentioned in one of the sets, mention it in all of the sets, even if it's default in TF2, it's what is set in the other sets of commands, it has a very small impact on the game and it's barely used/known, etc...
* (optional) Write why did you test these commands, what do they do, post screenshots of the game with each set...
* **Write the results of the benchmark for each set of commands. If it's a live match benchmark, write the FPS as well.**
* How was the command tested (demo, casual, match with bots...)? If it was tested by a demo which isn't the demo above, then link the demo and write why.
* Config version (don't say latest, say the actual version, found at the top of `mastercomfig/cfg/comfig.cfg`, like 6.1.1)
* Config preset and addons
* Custom values (if any) including TF2 settings that don't appear in your config (you can screenshot if you want)
* If you have many custom values and commands create another gist that is your config. Link to it using this method:
  `[text you want to be linked, for example, "my config"](link)`
* Addons, mods, scripts, programs and processes running in the background...
* DX level (available in advanced video settings)
* Launch options
* Operating system (OS)
* Graphics card (GPU)
* Processor (CPU)
* HDD or SSD
* RAM size in MB or GB




## How to Make a Preview of the Benchmark


* *So you made the gist and you want to post it. what do you do now?*
* Firstly, go to the wiki page ["Benchmarks"](https://github.com/mastercoms/tf2cfg/wiki/Benchmarks)
* Click on "Edit" near the top right.
* Scroll down to under the instructions and all the other benchmarks and:
* (optional) Write your username
* Write the date/s when you tested the commands
* Write the set of commands you were trying to test.
* Write how you tested them (demo, server, bots match...)
* Write your operating system (OS)
* Write your DX level
* Link to the gist where you've written all the information about the benchmark
* Press "Save Page" near the bottom right of the page
* **DONE!**



Although the instructions are clear and are written using formal language, I would recommend taking them with a grain of salt, and if you want to add / subtract something in your benchmark and it has a reasonable reason, you are welcome to do that (even thought adding information to your benchmarks can't hurt anyone, and subtracting can...).

* #### Help:
[A basic GitHub formatting guide](https://help.github.com/articles/basic-writing-and-formatting-syntax/)


[A page in the TF2 wiki about demos](https://wiki.teamfortress.com/wiki/Help:Recording_demos)