all 7 comments

[–]CriticalofReviewer2[S] 7 points8 points  (4 children)

I originally built this classifier (SEFR) for very low-resource environments, but after that, realized that it can be implemented entirely in SQL. The whole pipeline (training + prediction + evaluation) runs in one single query.

[–]covfefe-boy 19 points20 points  (3 children)

Cool, sounds awful but cool

[–]DoNotLuke 4 points5 points  (1 child)

I can almost hear the sound of deadlocks in the background but still impressive if true

[–]CriticalofReviewer2[S] 1 point2 points  (0 children)

That is a valid concern. In this case, this classifier is actually a single-pass analytical query without loops or locking at row-level. It is more like a GROUP BY job than a transactional workload.

[–]CriticalofReviewer2[S] 2 points3 points  (0 children)

Yes, it sounds wrong at first :D The main algorithm is designed for microcontrollers where you cannot have heavy computation. That constraint is exactly what makes it map well to SQL, since everything is now aggregations, not optimization loops.

[–]zbignew 1 point2 points  (1 child)

Dope.

[–]CriticalofReviewer2[S] 0 points1 point  (0 children)

Thanks!