Slow compilation for NuSVM generated code

Questions & Help Questions
2

The first thing that comes to mind in the SVM code is:

  1. you are converting everything to a binary first thing. don’t do that for anything from m2cgen. if the goal is to work with large amounts of data, lists are not a good representation, at all. Instead expect the input to be a binary.

  2. you are reading the same input multiple times. This was not a problem in the other examples but seems to be one for SVM. So I would do this as the first thing on top:

<<v1::float, v2::float, v3::float, ...>> = input

And then use v1, v2, instead of calling read. Not sure how much it helps, but it should help a bit.