Would you mind also posting the network tuning parameters you're using
along with the os? I know that when I do perf testing for go on linux, I
typically need to update a number of tcp related kernel parameters before I
get meaningful numbers.
M
--
You received this message because you are s
Sure, will post when i do it. Will open a new thread then :)
On Monday, January 14, 2019 at 7:49:36 PM UTC+5:30, Rodolfo Azevedo wrote:
>
> Please, when you finish your workerpool can you share your code to me? I
> need to understand this.
>
> Thanks and Regards
>
> Rodolfo Azevedo
>
> Em seg, 14
Please, when you finish your workerpool can you share your code to me? I
need to understand this.
Thanks and Regards
Rodolfo Azevedo
Em seg, 14 de jan de 2019 às 10:16, Kasun Vithanage
escreveu:
> I've deleted original post because it seems a problem with my code, will
> try to use a WorkerPoo
I've deleted original post because it seems a problem with my code, will
try to use a WorkerPool and see the result :)
Thanks for support
On Monday, January 14, 2019 at 6:38:27 PM UTC+5:30, Jesper Louis Andersen
wrote:
>
> This might not be due to Go, but rather due to a resource limit imposed
I would also try to test the load on a different host too.
On Monday, January 14, 2019 at 6:38:27 PM UTC+5:30, Jesper Louis Andersen
wrote:
>
> This might not be due to Go, but rather due to a resource limit imposed by
> the operating system:
>
> # 5000. *. (1. -. 0.1954);;
> - : float = 4023.
>
I was wondering about it too, but I see Sun's HTTP Server can handle almost
every request with even some work load under the same machine. It uses a
ThreadPool for the task while go uses goroutines.
On Monday, January 14, 2019 at 6:38:27 PM UTC+5:30, Jesper Louis Andersen
wrote:
>
> This might
This might not be due to Go, but rather due to a resource limit imposed by
the operating system:
# 5000. *. (1. -. 0.1954);;
- : float = 4023.
This is close to 4096, assuming a constant factor of other stuff needing
resources. Also, as a first step, I'd recommend running your load generator
on a
I'm doing a simple load test with Apache JMeter. My ambition was to
benchmark a go server. Here is the code I've been using, its a simple web
server
package main
import (
"fmt"
"log"
"net/http"
"runtime"
)
func handler(w http.ResponseWriter, r *http.Request) {
fmt.Fprintf(w, "welcome")
