4 ms·
Increase your testing speed by 50% by replacing your `#!/bin/bash` (or whatever) with `#!/bin/true` and reducing your script to 1 line.
by tenebrisalietum 3y ago
Increase your testing speed by 50% by replacing your `#!/bin/bash` (or whatever) with `#!/bin/true` and reducing your script to 1 line.
- datadrivenangel 3y agoyou can go even faster by piping to \dev\null! It's very performant.
- Karellen 3y agoIs piping to /dev/null webscale?
- rcbdev 3y agoDoes it support sharding?
- jerf 3y agoIt is literally impossible to support sharding better than /dev/null does.
- LargeTomato 3y agoWe just need an elastic load balancer, a reverse proxy, a couple /dev/null sinks, observability & metrics, backup, green-blue deployments, auditability, staging and preprod environments, and a month or so of SWE time. That will be well over $20k from the corporate salary budget, thank you!
- justin_oaks 3y agohttps://devnull-as-a-service.com/ https://devnull-as-a-service.com/
- quickthrower2 3y agoNice traditional setup. No Microservice Workflow Orchestration. (Yes that is a thing)
- marcosdumay 3y agoThat would stop the GP from logging the errors as "warnings" and treating them without triggering his boss. And yeah, I can totally see somebody doing it on practice. I have seen people do lots of similar things.
- quickthrower2 3y ago#!/bin/yes works too, if you want to kill the KPI script