You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
LightGBM has already released v3.1.1 which contains a lot of new features and performance improvement. It seems mmlspark is still using v.2.3.1(the lightgbmlib version using now is 2.3.180, not sure if it's a release of v.2.3.1).
Describe the solution you'd like
Build a jar base on v3.1.1 and deploy it into Maven central.
Additional context
I have post an issue to LightGBM but they cant' help with this because they don't own the Maven central: microsoft/LightGBM#3791 (comment).
We have a pure Java LightGBM implementation which can only do predict for binary model, and I did a simple benchmark to compare the performance between pure Java implementation and lightgbmlib-2.3.180. The result is that the Java implementation is faster. I will take some time to do a benchmark with v3.1.1 in the near future.
Here is the result:
Is your feature request related to a problem? Please describe.
LightGBM has already released v3.1.1 which contains a lot of new features and performance improvement. It seems mmlspark is still using v.2.3.1(the lightgbmlib version using now is 2.3.180, not sure if it's a release of v.2.3.1).
Describe the solution you'd like
Build a jar base on v3.1.1 and deploy it into Maven central.
Additional context
I have post an issue to LightGBM but they cant' help with this because they don't own the Maven central: microsoft/LightGBM#3791 (comment).
We have a pure Java LightGBM implementation which can only do predict for binary model, and I did a simple benchmark to compare the performance between pure Java implementation and lightgbmlib-2.3.180. The result is that the Java implementation is faster. I will take some time to do a benchmark with v3.1.1 in the near future.

Here is the result:
Show JSON
The text was updated successfully, but these errors were encountered: