Performance benchmarking (fit)

Open
#14 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
julia, scikit-learn

Research direction

Start by defining a systematic benchmarking approach for the listed regression and classification methods, including function, gradient, and Hessian call counts and objective convergence. Compare the implementations against scikit-learn and quantreg, and consider the issue complete when the listed cases have reproducible measurements or convergence plots against the stated expectations.

Written by the indexing model from the issue text.

Description

long-term

Before starting this, need a way to systematically:

  • trace number of function calls, number of gradient calls, number of hessian calls
  • have a way to stop with universal criterion OR show a plot where the objective function decreases and eventually hits the same value as that from ref package.
Against scikitlearn

expect on par or better

  • ridge (in big case should see improvements from using CG)
    • analytical (should see no real diff)
    • CG
  • lasso
    • FISTA
    • ISTA
  • elnet
  • logistic (no or l2 penalty)
    • (cannot test Newton)
    • Newton CG see issue #24
    • LBFGS
  • logistic (elnet penalty)
    • FISTA
    • ISTA
  • multinomial (no or l2 penalty)
    • Newton CG see issue #24
    • LBFGS
  • multinomial (elnet penalty)
    • FISTA
    • ISTA
Against quantreg

expect a bit worse (quantreg is effectively in cpp)

  • quantile regression
Dominant language
Julia
Stars
86
Forks
16
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from JuliaAI/MLJLinearModels.jl

All issues in JuliaAI/MLJLinearModels.jl

Similar issues

More Julia issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.