Vlad Lasky

@harryadel this PR concerns the DDP layer, which is above the WebSocket layer, which is what your proposal seems to be concerned with.

> Yeah at least 2 is from here. I've added this line here to try to find where are problems coming from > > https://github.com/meteor/meteor/blob/1d4aa133de2f29571f9962f97540207badffbbd0/packages/test-in-console/puppeteerRunner.js#L32 Any new details that have...

> Hey I believe integrated GPU are **not** supported, probably better to run on CPU at this time, by passing -ngl 0 instead of 9999 OK. I was curious to...

What's preventing this from being merged?

Welcome @hectoroso! `vlasky:mysql` certainly is supported and is being used by many businesses in various Meteor production apps.

@hectoroso `Meteor.subscribe()` is definitely the correct function to use on the client side, but that numtel MySQL leaderboard example code is old and needs a number of fixes to work...

> We have millions of queries on this DB per day, but about once per day, we get a deadlock error with a query where we're not using locks. The...

Having taken a quick look at Meteor's source code, I see that JSON.parse() is called all over the place, so I expect the performance gains could be even greater. Given...

@mitar I don't think it's premature at all. In all these years Meteor has been around, it hasn't been previously considered. The event loop is the most important place to...

Here are the published benchmarks for using simdjson within the node process via the binding **simdjson_nodejs**. To me, these results are conclusive. https://github.com/luizperes/simdjson_nodejs#benchmarks