What kind of memory footprint would something like this have?
I'm assuming you didn't use 50GB of RAM and the processing was line-by-line, which should be quite small.
I'm assuming you didn't use 50GB of RAM and the processing was line-by-line, which should be quite small.
Go outperformed our previous solution by over 60x, making our new bottleneck disk I/O instead of CPU.
When we benchmarked them, what would take PHP 30 minutes, Go could do in less than 30 seconds. Only the transform is written in Go, the rest of the ETL is still in PHP.
This bubble sort benchmark between PHP and Go supports your claims.