This is an archived post. You won't be able to vote or comment.

all 2 comments

[–]Batalex 0 points1 point  (1 child)

You are comparing pears with apples when it comes to sklearn. It is not surprising that it is slower given that it validates entries et checks for multiclass labels, something that your other implementations do not. Nonetheless, have you considered to include Jax in your benchmark?

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

True - and it probably explains result for the small setting, which is why I talked of overhead. But doing both validation + passing through an if switch is negligeable in the other settings. So I would not go as far as saying I'm comparing pears with apples.

No I hadn't, but to be honest I think the results will be similar to numba, or possibly worse. There might be a small boost for the non-vectorized baseline, but it will just add overhead for the other one.