Testing kito not just static tiny responses but with large body paylod

[Flora90001]

Nice to hear that Rust running under node Js.

1. Does this support streaming?
2. Since you rely on one shot is there a timeout option to save rust core from being choked by dead node Js event loop.
3. The test results seems to be not okay because comparing with uws against tiny string or static responses makes no sense. Try testing post method that returns the large req paylod directly to client back in json. That's how TechEmpower bench marks compare raw compute.
4. Uws Js support clustering directly from Node Js. When I tried the same with kito it throws error. Address /port already in use. So there fore no cluster possible.
5. I ran the bench marks in my ec2 instance c7gx.large. Against bun elysia post requests your kito literally scored only 32k req/s where as elysia literally doubled that.
6. But I know hyper is more capable but compared to may mini it's not that fast. (Note may mini crate doesn't support windows) it's fully Unix based.

Plz do clarify my questions waiting for your answers also I want to have serve static to serve files

[mindplay-dk]

I'm also looking for stream support - looks like we only have Buffer and string support for now:

kito/packages/kitojs/src/server/response.ts

Lines 248 to 259 in 3d5b53f

	send(data: unknown): void {
	this.checkFinished();
	if (Buffer.isBuffer(data)) {
	this.state.body = data;
	} else if (typeof data === "string") {
	this.state.body = Buffer.from(data, "utf-8");
	} else {
	this.state.body = Buffer.from(String(data), "utf-8");
	}
	this.serializeAndSend();
	}

Streams are likely also required for an efficient static file server? Serving files (images/audio/video) from RAM is a no-go. 😅

Not sure about the rest of the notes in this bulk issue, but streams and a static file server probably should have open issues?

(is there a roadmap? the API and codebase looks overall great already, I'm really excited to see where this project goes!)

[Flora90001]

I'm also looking for stream support - looks like we only have Buffer and string support for now:

kito/packages/kitojs/src/server/response.ts

Lines 248 to 259 in 3d5b53f

send(data: unknown): void {
this.checkFinished();
if (Buffer.isBuffer(data)) {
this.state.body = data;
} else if (typeof data === "string") {
this.state.body = Buffer.from(data, "utf-8");
} else {
this.state.body = Buffer.from(String(data), "utf-8");
}

this.serializeAndSend();
}
Streams are likely also required for an efficient static file server? Serving files (images/audio/video) from RAM is a no-go. 😅

Not sure about the rest of the notes in this bulk issue, but streams and a static file server probably should have open issues?

(is there a roadmap? the API and codebase looks overall great already, I'm really excited to see where this project goes!)

Well this project is using Tokio one shot per req. Where the respond buffer is sent in full round. So streaming is merely possible unlike node Js which supports streams by default. Here hyper + Tokio is utilized for max speed and throughput. Although Hyper supports streaming Implementing that Here is kinda massive workload. Involves rewriting architecture flow.

Try testing this framework with large post pay loads json computing that returns the same body. With other Frameworks in cluster mode you will get a clear vision using wrk.

[nehu3n]

Hi @Flora90001 ! Thank you so much for your interest. 🙂

1. Currently, Kito doesn’t support streaming. As you mentioned, it uses a one-shot approach to send responses. I’ll need to rewrite part of the architecture to enable it, but rest assured it will be supported in future versions!

2. There isn’t a mechanism yet to prevent blocking, but I’ve added it to the list of pending improvements.

3. Clustering hasn’t been implemented yet either, but I’ll prioritize adding it as a feature as soon as possible. 🙌🏻

4. Could you share the code, tool, and environment you used for the benchmark? I’d love to take a look. What you observed is possible — there are still many optimizations left to implement.

Serving static files should currently work unless there’s a bug. That said, it’s not the most efficient approach yet, so it will need to be revisited. Overall, there is a lot of work to be done 😅

[nehu3n]

Hi @Flora90001 and @mindplay-dk !

Just wanted to let you know that I’ve added support for streaming, SSE, and clustering. You can check out the examples here (streaming/SSE) and here (clustering).

These features will be available in the next release. Thanks!

[mindplay-dk]

@nehu3n wow, you don't waste any time! 😄

Will you make res.send() support streams as well? That would be mostly for convenience, I suppose - but it is convenient if you're going to proxy a server, e.g. for auth middleware in front of protected local or remote file storage.

The type on the send param probably could be made a little clearer than just unknown as well? 🙂

But this is almost at a point where I might try to port my express project to see how that goes. 🙃

[mindplay-dk]

I think we'll need support for res.sendFile as well?

https://expressjs.com/en/api.html#res.sendFile

[nehu3n]

@mindplay-dk What do you mean? Kito already implements res.sendFile(), as shown in this example .

Or are you referring to Express compatibility? 🤔

[Flora90001]

@mindplay-dk What do you mean? Kito already implements res.sendFile(), as shown in this example .

Or are you referring to Express compatibility? 🤔

I'm waiting for next reelase but no clues.. Also your bench marks shows huge diff now. Express fastify getting closer. So you just dropped the existing one shot architecture with socket2 mpmc? One to support streams. Did that increased Rps or not?