Skip to content

Commit fae849a

Browse files
Sarthak | Updates README
1 parent 6c6d3ef commit fae849a

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

Diff for: README.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -108,7 +108,7 @@ This means, we can have 100 workers with 10 connections, where a group of 10 wor
108108

109109
You can refer the code [here](https://github.com/SarthakMakhija/blast/blob/main/workers/worker_group.go#L89).
110110

111-
5. **My server takes a protobuf encoded byte slice. How do I pass the payload to blast?**
111+
4. **My server takes a protobuf encoded byte slice. How do I pass the payload to blast?**
112112

113113
**blast** supports reading the payload from a file. The payload that needs to be sent to the target server can be written to a file in a separate process and then the file can be passed
114114
as an option to the **blast**. Let's look at the pseudocode:
@@ -132,18 +132,18 @@ as an option to the **blast**. Let's look at the pseudocode:
132132

133133
The above code creates a protobuf encoded message and writes it to a file. The file can then be provided using `-f` option to the **blast**.
134134

135-
6. **blast provides a feature to read responses. How is response reading implemented?**
135+
5. **blast provides a feature to read responses. How is response reading implemented?**
136136

137137
[ResponseReader](https://github.com/SarthakMakhija/blast/blob/main/report/response_reader.go) implements one goroutine per `net.Conn` to read responses from connections.
138138
The goroutine keeps on reading from the connection, and tracks successful and failed reads. This design means that there will be 1M response reader goroutines if the user
139139
wants to establish 1M connections and read responses. To handle this, IO multiplexing + pool of ResponseReaders is planned in subsequent release.
140140

141-
7. **What is the significance of Rrs flag in blast?**
141+
6. **What is the significance of Rrs flag in blast?**
142142

143143
To read responses from connections, **blast** needs to know the response payload size. The flag `Rrs` signifies the size of the response payload in bytes (or the size of the
144144
byte slice) that [ResponseReader](https://github.com/SarthakMakhija/blast/blob/main/report/response_reader.go) should read in each iteration.
145145

146-
8. **What is the significance of Rrd flag in blast?**
146+
7. **What is the significance of Rrd flag in blast?**
147147

148148
`Rrd` is the read response deadline flag that defines the deadline for the read calls on connections.
149149
This flag helps in understanding the responsiveness of the target server. Let's consider that we are running **blast** with the following command:

0 commit comments

Comments
 (0)