aduh95
commented
11 months ago You mean node:worker_threads, right? If all buffers could be shared, the language would not have bothered to come up with a SharedArrayBuffer implementation. What you can do is the following:
function sabToBuffer(sab) {
return new Uint8Array(sab);
}Uint8Array is not exactly a Buffer, but I don't think you'll find any Node.js API that accept Buffer and not Uint8Array (if you do, that'd be a bug, please report it).
On the other hand, if you have a Buffer/Uint8Array and want to transfer its content to an other thread, you have two options:
// Option 1: copy the content to a SharedArrayBuffer:
function copyBufferToSAB(buffer, sab) {
if (buffer.byteLength > sab.byteLength) throw new Error('Buffer overflow');
new Uint8Array(sab).set(buffer);
}
// Option 2: transfer the underlying array buffer:
function transferBuffer(buffer) {
otherThread.postMessage(buffer, [buffer.buffer]);
}Option 2 is way faster, but note that only one thread interact with a non-sharable buffer, meaning that once it is transfered, the original thread can no longer have access to that buffer data.
introspection3
RedYetiDev
What is the problem this feature will solve?
threads_worker is used by many people,but we can only use SharedArrayBuffer ,but Buffer is node's first citizen（socket eg）,can you share Buffer to SharedArrayBuffer ?
What is the feature you are proposing to solve the problem?
let instance=SharedArrayBuffer.from(Buffer instance);//zero copy let instance2=Buffer.From(SharedArrayBuffer instance);//zero copy
What alternatives have you considered?
No response