# Introduction to Vectorization in ArrayFire

Programmers and Data Scientists want to take advantage of fast and parallel computational devices. One of the best ways of doing this is to write vectorized code; however, this is often easier said than done. In today's continuation of the blog series "Learning ArrayFire from scratch", we will discuss the various methods by which you can maximize the performance of your code by using ArrayFire's built-in vectorization features.

ArrayFire provides many ways to vectorize a given code segment. In this tutorial, we present several methods to vectorize code using ArrayFire and discuss the benefits and drawbacks associated with each method.

#### Generic/Default vectorization

By its very nature, ArrayFire is a vectorized library. Most functions operate on arrays as a whole – on all elements in parallel. Wherever possible, existing vectorized functions should be used opposed to manually indexing into arrays. For example consider the following code:

Although completely valid, the code is very inefficient as it results in a kernel that operate on one datum. Instead, the developer should have used ArrayFire's overload of the + operator:

This code will result in a single kernel that operates on all 10 elements of `a` in parallel.

Most ArrayFire functions are vectorized. A small subset of these include:

Arithmetic operations: +, -, *, / , %, >>, <<
Logical operations: &&, ||, <, >, ==, !=
Numeric functions: abs(), floor(), round(), min(), max()…
Complex operations: real(), imag(), conj()…
Exponential and logarithmic functions: exp(), log(), expm1(), log1p()…
Trigonometric functions: sin(), cos(), tan()…
Hyperbolic functions: sinh(), cosh(), tanh()…

In addition to element-wise operations, many other functions are also vectorized in ArrayFire.

Notice that even that performs some form of aggregation (e.g. `sum()` or `min()`), signal processing (like `convolve()`), and even image processing functions (i.e. `rotate()`) all support vectorization on different columns or images. For example, if we have `NUM` images of size `WIDTH` by `HEIGHT`, one could convolve each image in a vector fashion as follows:

Similarly, one can rotate 100 images by 45 degrees in a single call using code like the following:

Although most functions in ArrayFire do support vectorization, some do not. Most notably, all linear algebra functions. Even though they are not vectorized linear algebra operations still execute in parallel on your hardware.

Using the built in vectorized operations should be the first and preferred method of vectorizing any code written with ArrayFire.

#### GFOR: Parallel for-loops

Another novel method of vectorization present in ArrayFire is the GFOR loop replacement construct. GFOR allows launching all iterations of a loop in parallel on the GPU or device, as long as the iterations are independent. While the standard for-loop performs each iteration sequentially, ArrayFire's gfor-loop performs each iteration at the same time (in parallel). ArrayFire does this by tiling out the values of all loop iterations and then performing computation on those tiles in one pass. You can think of gfor as performing auto-vectorization of your code, e.g. you write a gfor-loop that increments every element of a vector but behind the scenes ArrayFire rewrites it to operate on the entire vector in parallel.

The original for-loop example at the beginning of this document could be rewritten using GFOR as follows:

In this case, each instance of the gfor loop is independent, thus ArrayFire will automatically tile out the `a` array in device memory and execute the increment kernels in parallel.

To see another example, you could run an accum() on every slice of a matrix in a for-loop, or you could "vectorize" and simply do it all in one gfor-loop operation:

However, returning to our previous vectorization technique, accum() is already vectorized and the operation could be completely replaced with merely:

It is best to vectorize computation as much as possible to avoid the overhead in both for-loops and gfor-loops. However, the gfor-loop construct is most effective in the narrow case of broadcast-style operations. Consider the case when we have a vector of constants that we wish to apply to a collection of variables, such as expressing the values of a linear combination for multiple vectors. The broadcast of one set of constants to many vectors works well with gfor-loops:

Using GFOR requires following several rules and multiple guidelines for optimal performance. The details of this vectorization method can be found in the GFOR documentation.

#### Batching

The batchFunc() function allows the broad application of existing ArrayFire functions to multiple sets of data. Effectively,batchFunc() allows ArrayFire functions to execute in "batch processing" mode. In this mode, functions will find a dimension which contains "batches" of data to be processed and will parallelize the procedure.

Consider the following example. Here we create a filter which we would like to apply to each of the weight vectors. The naive solution would be using a for-loop as we have seen previously:

However, as we have discussed above, this solution will be very inefficient. One may be tempted to implement a vectorized solution as follows:

However, the dimensions of `filter` and `weights` do not match, thus ArrayFire will generate a runtime error.

`batchfunc()` was created to solve this specific problem. The signature of the function is as follows:

where `batchFunc_t` is a function pointer of the form:

So, to use batchFunc(), we need to provide the function we wish to apply as a batch operation. For illustration's sake, let's "implement" a multiplication function following the format.

Our final batch call is not much more difficult than the ideal syntax we imagined.

The batch function will work with many previously mentioned vectorized ArrayFire functions. It can even work with a combination of those functions if they are wrapped inside a helper function matching the `__batchFunc_t__` signature. One limitation of `batchfunc()` is that it cannot be used from within a `gfor()` loop at the present time.