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
Tested with various connection counts (Bombardier's 'c' parameter) and the exe reports one req_read error for every connection, i.e, 5 errors for 5 connections, 20 for 20 connections and so forth.
Expected Behavior
To see Bombardier finish without pico emitting any error messages.
Current Behavior
Exe emits one 'Error during req_read' per connection
Increasing to 20k requests (20x1000 on a 24-core machine) sometimes shows something like this at the end of log output:
Error during req_read
Error during accept
Error during req_read
Error during req_read
Error during accept
Error during accept
Error during accept
Error during accept
Error during accept
Error during accept
Error during accept
Error during req_read
Error during req_read
Again, all requests are successful in the benchmark.
The underlying issue is that C recv and accept calls can reply with EAGAIN or EWOULDBLOCK on a -1 return value, which is to be expected for the asynchronous picoev event loop server.
The fix is to continue silently in the cases of EAGAIN or EWOULDBLOCK.
Describe the bug
Reproduction Steps
Tested the throughput of vweb/pico using Bomardier.
Built an exe from https://github.com/vlang/v/blob/master/examples/pico/pico.v (using tcc)
Tested with various connection counts (Bombardier's 'c' parameter) and the exe reports one req_read error for every connection, i.e, 5 errors for 5 connections, 20 for 20 connections and so forth.
Expected Behavior
To see Bombardier finish without pico emitting any error messages.
Current Behavior
Exe emits one 'Error during req_read' per connection
Possible Solution
Additional Information/Context
V version
0.4.5 2baa11b
Environment details (OS name and version, etc.)
Win11 Pro
Note
You can use the 👍 reaction to increase the issue's priority for developers.
Please note that only the 👍 reaction to the issue itself counts as a vote.
Other reactions and those to comments will not be taken into account.
The text was updated successfully, but these errors were encountered: