Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

net: fix bytesWritten during writev #14236

Closed
Closed
Show file tree
Hide file tree
Changes from 3 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 14 additions & 5 deletions lib/net.js
Original file line number Diff line number Diff line change
Expand Up @@ -825,11 +825,20 @@ protoGetter('bytesWritten', function bytesWritten() {
bytes += Buffer.byteLength(el.chunk, el.encoding);
});

if (data) {
if (data instanceof Buffer)
bytes += data.length;
else
bytes += Buffer.byteLength(data, encoding);
if (Array.isArray(data)) {
// was a writev, iterate over chunks to get total length
for (var i = 0; i < data.length; i++) {
const chunk = data[i];

if (data.allBuffers || chunk instanceof Buffer)
bytes += chunk.length;
else
bytes += Buffer.byteLength(chunk.chunk, chunk.encoding);
}
} else if (data instanceof Buffer) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These instanceof checks are going to be expensive on perf

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This specific check wasn't added in this PR, it was just down-indented (no perf change).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if we could get away with using data != undefined && typeof data !== 'string' instead? If so, we could first branch on the first condition and then do a if (typeof data !== 'string') { ... } else { ... } to avoid duplicate if (data)-style checks.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mscdex Yes, .write() will error if it's neither a Buffer nor a string, so this works! I've updated it with the optimization.

bytes += data.length;
} else if (data) {
Copy link
Contributor

@mscdex mscdex Jul 14, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps this can be simplified a bit by merging with the if/else below:

if (Array.isArray(data)) {
  // ...
} else if (data instanceof Buffer) {
  // ...
} else if (data) {
  // ...
}

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good tip! I just collapsed the branches.

bytes += Buffer.byteLength(data, encoding);
}

return bytes;
Expand Down
35 changes: 35 additions & 0 deletions test/parallel/test-net-socket-byteswritten.js
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
'use strict';

const common = require('../common');
const assert = require('assert');
const net = require('net');

const server = net.createServer(function(socket) {
socket.end();
});

server.listen(0, common.mustCall(function() {
const socket = net.connect(server.address().port);

// Cork the socket, then write twice; this should cause a writev, which
// previously caused an err in the bytesWritten count.
socket.cork();

socket.write('one');
socket.write(new Buffer('twø', 'utf8'));

socket.uncork();

// one = 3 bytes, twø = 4 bytes
assert.strictEqual(socket.bytesWritten, 3 + 4);

socket.on('connect', common.mustCall(function() {
assert.strictEqual(socket.bytesWritten, 3 + 4);
}));

socket.on('end', common.mustCall(function() {
assert.strictEqual(socket.bytesWritten, 3 + 4);

server.close();
}));
}));