Closed hachi8833 closed 7 years ago
hachi8833
commented
7 years ago It is a little bit strange that the occurrence of the panic looks not random. For example, I remember:
st0012
commented
7 years ago @hachi8833 I think current master should no longer has this issue, can you help me confirm it?
hachi8833
commented
7 years ago Performed make test twelve-times and all passed. Excellent!
Completed 3000 requests
Finished 3000 requests
Server Software:
Server Hostname: localhost
Server Port: 3000
Document Path: /
Document Length: 15 bytes
Concurrency Level: 100
Time taken for tests: 2.425 seconds
Complete requests: 3000
Failed requests: 0
Total transferred: 396000 bytes
HTML transferred: 45000 bytes
Requests per second: 1237.16 [#/sec] (mean)
Time per request: 80.830 [ms] (mean)
Time per request: 0.808 [ms] (mean, across all concurrent requests)
Transfer rate: 159.48 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 5 2.2 6 11
Processing: 0 57 222.6 6 1143
Waiting: 0 56 222.7 6 1143
Total: 0 62 222.7 12 1147
Percentage of the requests served within a certain time (ms)
50% 12
66% 13
75% 14
80% 14
90% 16
95% 21
98% 1014
99% 1068
100% 1147 (longest request)I close the issue.
I'd open the issue now because the 'thread' branch has been merged into 'master' branch. The frequency of the panic
fatal error: concurrent map read and map writeis getting less and less, but occasionally occurs.(Goby's
make testis getting more stable than before.)