2 ms·
I hate to say this, but for some reason I can't help myself. This looks like a problem for which I could write the code in 15 minutes. Assuming Markham's Rule
by DanielBMarkham 16y ago
I hate to say this, but for some reason I can't help myself.
This looks like a problem for which I could write the code in 15 minutes. Assuming Markham's Rule of Estimating (double the number and go to then next larger unit), that's about 30 hours of work.
This is a problem just begging for a functional solution. If you've got a language that already has a bunch of libraries, like .NET, you just wire it up, pipeline it, and send it out to as many workers as you want. The image tweaking, worker nitpicking stuff just isn't worth the time. If you're doing millions of everything, then I'm sure you've already got some broker parallelization thing going on. Shouldn't need to redo that every time. If you want to be truly anal, do some tests to determine the fastest way to compress. But aside from that, it's all big old hunks of immutable data splaying out into the universe, running on as many cores as you need.
I probably missed something. These things always look simpler from the outside.