Harry Waye 7ba6fa7148 chore(plugin-server): remove piscina workers (#15327) ... * chore(plugin-server): remove piscina workers Using Piscina workers introduces complexity that would rather be avoided. It does offer the ability to scale work across multiple CPUs, but we can achieve this via starting multiple processes instead. It may also provide some protection from deadlocking the worker process, which I believe Piscina will handle by killing worker processes and respawning, but we have K8s liveness checks that will also handle this. This should simplify 1. prom metrics exporting, and 2. using node-rdkafka. * remove piscina from package.json * use createWorker * wip * wip * wip * wip * fix export test * wip * wip * fix server stop tests * wip * mock process.exit everywhere * fix health server tests * Remove collectMetrics * wip		2023-05-03 14:42:16 +00:00
..
assets
helpers	chore(plugin-server): remove piscina workers (#15327)	2023-05-03 14:42:16 +00:00
main	chore(plugin-server): remove piscina workers (#15327)	2023-05-03 14:42:16 +00:00
utils
worker	chore(plugin-server): remove piscina workers (#15327)	2023-05-03 14:42:16 +00:00
config.test.ts
e2e.buffer.test.ts
e2e.timeout.test.ts
historical-export-e2e.test.ts	chore(plugin-server): remove piscina workers (#15327)	2023-05-03 14:42:16 +00:00
http-server.test.ts	chore(plugin-server): remove piscina workers (#15327)	2023-05-03 14:42:16 +00:00
server.test.ts	chore(plugin-server): remove piscina workers (#15327)	2023-05-03 14:42:16 +00:00
sql.test.ts
utils.test.ts