Patryk Cieszkowski

We can gather basic metadata with node's `os` module. ``` const os = require('os') const cpuCount = os.cpus().length ```

It also outputs the clock speed, and available resources ``` [ { model: 'Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz', speed: 4268, times: { user: 150659900, nice: 277600, sys: 65754400, idle:...

https://nodejs.org/docs/latest-v12.x/api/worker_threads.html

I have a stupidly simple idea. We could brute-force as many requests as possible on probe's initial run, until their CPU usage reaches certain level, and store those values in...

Both of you are correct. Due to nature of the project - we can't possibly predict how performant the probe is going to be, but at the same time we...

How often would we collect CPU/mem stats? And how often would we pushe them to the API? Also, how exactly do we define uptime? How long has the probe been...

@MartinKolarik any idea how to reasonably store this data? Ideally we would keep it all under a single record, but since we need older data to expire, we can't do...

> > each command execution spawns a separate process, > > the master process just handles the connection to the server and passes data back and forth > > so...

@jimaek as explained - it’s done

HTTP is an I/O request - it’s asynchronous like web sockets are. It’s not recommended to run I/O requests on separate threads, since native aync mechanism is much more performant....