You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -108,7 +108,7 @@ This means, we can have 100 workers with 10 connections, where a group of 10 wor
108
108
109
109
You can refer the code [here](https://github.com/SarthakMakhija/blast/blob/main/workers/worker_group.go#L89).
110
110
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?**
112
112
113
113
**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
114
114
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:
132
132
133
133
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**.
134
134
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?**
136
136
137
137
[ResponseReader](https://github.com/SarthakMakhija/blast/blob/main/report/response_reader.go) implements one goroutine per `net.Conn` to read responses from connections.
138
138
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
139
139
wants to establish 1M connections and read responses. To handle this, IO multiplexing + pool of ResponseReaders is planned in subsequent release.
140
140
141
-
7.**What is the significance of Rrs flag in blast?**
141
+
6.**What is the significance of Rrs flag in blast?**
142
142
143
143
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
144
144
byte slice) that [ResponseReader](https://github.com/SarthakMakhija/blast/blob/main/report/response_reader.go) should read in each iteration.
145
145
146
-
8.**What is the significance of Rrd flag in blast?**
146
+
7.**What is the significance of Rrd flag in blast?**
147
147
148
148
`Rrd` is the read response deadline flag that defines the deadline for the read calls on connections.
149
149
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