Switch to using node.js core library `Agent` for socket pooling about fluent-logger-node HOT 7 CLOSED

Could you take the benchmark?
Is node's core Agent class http.Agent?
This module uses net.Socket because Fluentd does not speak HTTP(S).

from fluent-logger-node.

No response.

from fluent-logger-node.

Sorry, didnt see your question until I got the most recent GitHub notification.

And yes, that's right.

When you say
This module uses net.Socket because Fluentd does not speak HTTP(S).

Do you mean it speaks UDP, not TCP?

from fluent-logger-node.

This module uses TCP to talk with Fluentd.
All fluent-logger follow Forward protocol specification.

from fluent-logger-node.

Exactly. Instead of creating a new socket every time, you can use's Node's built in HTTP (TCP) module, which will manage socket reuse / pooling for you. This will make this module more efficient than creating a new socket every log -- which is not a good idea of high throughput servers. Socket reuse makes more sense

@JoshFerge does this make sense and do you concur?

from fluent-logger-node.

HTTP is constructed on TCP and also Fluentd's forward protocol is original protocol constructed on TCP.
Fluentd's forward protocol is not HTTP.
So we cannot use Node's build-in HTTP module for Fluentd's forward protocol.

from fluent-logger-node.

No response.

from fluent-logger-node.