So far we used a separate eventloop from node.js's eventloop for handling webtransport io and processing.
This produced a lot of overhead.
Now, a restructuring of the plugin was made to use for the sockets and the event loop node.js internal stuff.
It is not benchmarked yet (and some optimizations are pending), but it is hoped to improve performance.
So far we used a separate eventloop from node.js's eventloop for handling webtransport io and processing. This produced a lot of overhead. Now, a restructuring of the plugin was made to use for the sockets and the event loop node.js internal stuff. It is not benchmarked yet (and some optimizations are pending), but it is hoped to improve performance.