Live data from Hacker News

A large scale non-linear optimization library

github.com

1–10 of 34 posts

Re: A large scale non-linear optimization library

#4
post #3

For all of the success applying GPUs to optimization problems in ML, why don't any of the common optimization packages seem to support GPU acceleration?

Less users. Smaller matrices.

There are a lot of large-scale optimization problems in industry that are still compute bound. Currently available solvers are either single threaded on the CPU, or offer "parallelism" by running copies of the same problem on multiple threads, but with different initial conditions in hopes that one happens to converge faster.

Re: A large scale non-linear optimization library

#6

For all of the success applying GPUs to optimization problems in ML, why don't any of the common optimization packages seem to support GPU acceleration?

For combinatorial optimization, there is now NVIDIA cuOpt, which is ridiculously fast: https://developer.nvidia.com/cuopt-logistics-optimization

Ceres can use GPUs for some solver bits too, I believe.

Re: A large scale non-linear optimization library

#7

For all of the success applying GPUs to optimization problems in ML, why don't any of the common optimization packages seem to support GPU acceleration?

Optimization is an iterative path-dependent problem, it's not particularly GPU-friendly.

Re: A large scale non-linear optimization library

#9
post #3

Earlier quoted context omitted.

Less users. Smaller matrices.

There are a lot of large-scale optimization problems in industry that are still compute bound. Currently available solvers are either single threaded on the CPU, or offer "parallelism" by running copies of the same problem on multiple threads, but with different initial conditions in hopes that one happens to converge faster.

Most large-scale optimization outside of neural nets is bottlenecked by function evaluation

Re: A large scale non-linear optimization library

#10
post #7

For all of the success applying GPUs to optimization problems in ML, why don't any of the common optimization packages seem to support GPU acceleration?

Optimization is an iterative path-dependent problem, it's not particularly GPU-friendly.

What about interior point methods?
Post reply on HN