From 65fd1983b140a2fcd6c4cc71a2c44582d0879275 Mon Sep 17 00:00:00 2001 From: Alex Zvorygin Date: Mon, 9 Jul 2018 15:48:47 -0400 Subject: [PATCH] Fix broken link to goreplay.com -> goreplay.org --- docs/Distributed-configuration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Distributed-configuration.md b/docs/Distributed-configuration.md index 2795bf8..e08cc28 100644 --- a/docs/Distributed-configuration.md +++ b/docs/Distributed-configuration.md @@ -13,7 +13,7 @@ If you have multiple replay machines you can split traffic among them using `--s gor --input-raw :80 --split-output --output-tcp replay1.local:28020 --output-tcp replay2.local:28020 ``` -[GoReplay PRO](https://goreplay.com/pro.html) support accurate recording and replaying of tcp sessions, and when `--recognize-tcp-sessions` option is passed, instead of round-robin it will use a smarter algorithm which ensures that same sessions will be sent to the same replay instance. +[GoReplay PRO](https://goreplay.org/pro.html) support accurate recording and replaying of tcp sessions, and when `--recognize-tcp-sessions` option is passed, instead of round-robin it will use a smarter algorithm which ensures that same sessions will be sent to the same replay instance. In case if you are planning a large load testing, you may consider use separate master instance which will control Gor slaves which actually replay traffic. For example: