This is where the power and expressiveness of kdb+ shines. It has SIMD primitives out of the box and can optimize your code based on data types to take advantage of it. https://kx.com/blog/what-makes-time-series-database-kdb-so-f...
In our shop, we never look to vectorize any function or process unless it's called inside a loop many times.
There is none. That's a contradiction in terms. SIMD either fits the shape or it doesn't.
Try problem #1, parsing numbers.
That seems to disqualify your example