Goose Attack against a Genie App

Specific Domains Web Stack
21

Is it possible to obtain something like the 6 ms that @StatisticalMouse was reporting?

22

Let’s see!

@StatisticalMouse Please find PR here

23

Single threaded (removing --threads=auto which resulted in 8 threads) makes it even faster. I wonder why…

And the same is true for HTTP.jl (72ms at 8 threads vs 69 single threaded).

Genie prod own renderers single threaded:

image
image2036×1168 133 KB

24

The errors produced on Rust side on Mac are below for easy finding with Google.

error sending request for url (http://127.0.0.1:8000/): error trying to connect: tcp connect error: Operation timed out (os error 60)

and

error sending request for url (http://127.0.0.1:11000/): error trying to connect: tcp connect error: Can't assign requested address (os error 49)

The errors produced on Julia side are

┌ Error: 2021-06-26 11:34:25 Base.IOError("stream is closed or unusable", 0)
└ @ Genie.AppServer ~/.julia/packages/Genie/Uvtzb/src/AppServer.jl:93

and

┌ Error: error handling request
│   exception =
│    IOError: stream is closed or unusable
│    Stacktrace:
│      [1] check_open
│        @ ./stream.jl:386 [inlined]
│      [2] uv_write_async(s::TCPSocket, p::Ptr{UInt8}, n::UInt64)
│        @ Base ./stream.jl:1018
│      [3] uv_write(s::TCPSocket, p::Ptr{UInt8}, n::UInt64)
│        @ Base ./stream.jl:981
│      [4] unsafe_write(s::TCPSocket, p::Ptr{UInt8}, n::UInt64)
│        @ Base ./stream.jl:1064
│      [5] unsafe_write
│        @ ~/.julia/packages/HTTP/CGviq/src/ConnectionPool.jl:174 [inlined]
│      [6] write
│        @ ./strings/io.jl:185 [inlined]
│      [7] write
│        @ ./io.jl:637 [inlined]
│      [8] unsafe_write(http::HTTP.Streams.Stream{HTTP.Messages.Request, HTTP.ConnectionPool.Transaction{TCPSocket}}, p::Ptr{UInt8}, n::UInt64)
│        @ HTTP.Streams ~/.julia/packages/HTTP/CGviq/src/Streams.jl:110
│      [9] unsafe_write
│        @ ./io.jl:646 [inlined]
│     [10] write
│        @ ./io.jl:669 [inlined]
│     [11] handle(::HTTP.Handlers.RequestHandlerFunction{typeof(serveWelcome)}, ::HTTP.Streams.Stream{HTTP.Messages.Request, HTTP.ConnectionPool.Transaction{TCPSocket}})
│        @ HTTP.Handlers ~/.julia/packages/HTTP/CGviq/src/Handlers.jl:280
│     [12] handle(::HTTP.Handlers.Router{Symbol("##257")}, ::HTTP.Streams.Stream{HTTP.Messages.Request, HTTP.ConnectionPool.Transaction{TCPSocket}})
│        @ HTTP.Handlers ~/.julia/packages/HTTP/CGviq/src/Handlers.jl:467
│     [13] #4
│        @ ~/.julia/packages/HTTP/CGviq/src/Handlers.jl:346 [inlined]
│     [14] macro expansion
│        @ ~/.julia/packages/HTTP/CGviq/src/Servers.jl:413 [inlined]
│     [15] (::HTTP.Servers.var"#13#14"{HTTP.Handlers.var"#4#5"{HTTP.Handlers.Router{Symbol("##257")}}, HTTP.ConnectionPool.Transaction{TCPSocket}, HTTP.Servers.Server{Nothing, Sockets.TCPServer}, HTTP.Streams.Stream{HTTP.Messages.Request, HTTP.ConnectionPool.Transaction{TCPSocket}}})()
│        @ HTTP.Servers ./task.jl:411
└ @ HTTP.Servers ~/.julia/packages/HTTP/CGviq/src/Servers.jl:424
25

Yes, the stream closed error comes from HTTP.jl - I think it’s going to go away in the next release.

1 Like