SynapseML icon indicating copy to clipboard operation
SynapseML copied to clipboard

Adding dynamic allocation (autoscale) to LightGBM

Open imatiach-msft opened this issue 7 years ago • 18 comments

Fixes issue https://github.com/Azure/mmlspark/issues/319

imatiach-msft avatar Sep 06 '18 05:09 imatiach-msft

Excited to see this!

mhamilton723 avatar Sep 06 '18 18:09 mhamilton723

PASS Pass! — The build has succeeded. (4c8bd373)

MMLSpark 0.13.dev34+1.g4c8bd37

This is a build for Github PR #369, changes:

  • [4c8bd37] Ilya Matiach Adding dynamic allocation (autoscale) to LightGBM

mmlspark-bot avatar Sep 10 '18 23:09 mmlspark-bot

@imatiach-msft is this ready for a CR?

mhamilton723 avatar Sep 11 '18 21:09 mhamilton723

@mhamilton723 nope I need to test it more/refactor more, sorry, will let you know when

imatiach-msft avatar Sep 11 '18 21:09 imatiach-msft

PASS Pass! — The build has succeeded. (9034b114)

MMLSpark 0.14.dev14+1.g9034b114

This is a build for Github PR #369, changes:

  • [9034b114] Ilya Matiach Adding dynamic allocation (autoscale) to LightGBM

mmlspark-bot avatar Oct 26 '18 04:10 mmlspark-bot

PASS Pass! — The build has succeeded. (cdf42f3f)

MMLSpark 0.14.dev18+1.gcdf42f3f

This is a build for Github PR #369, changes:

  • [cdf42f3f] Ilya Matiach Adding dynamic allocation (autoscale) to LightGBM

mmlspark-bot avatar Oct 30 '18 06:10 mmlspark-bot

@imatiach-msft is this still being pursued?

peay avatar Feb 21 '19 12:02 peay

@peay yes but this involves a lot more testing and validation? I was hoping to use barrier execution mode from spark 2.4 instead of this PR but it doesn't support dynamic allocation, so it would just make things worse.

imatiach-msft avatar Feb 21 '19 21:02 imatiach-msft

I see. Is this branch working? Are there some known issues or things you'd like to have tested? I can try and see if I can test it on my end if that is helpful

peay avatar Mar 05 '19 07:03 peay

@peay sorry, this branch isn't close to a working state and can't be tested yet. I plan to look into this at some point though. Are you not able to disable dynamic allocation on your cluster?

imatiach-msft avatar Mar 05 '19 15:03 imatiach-msft

Static allocation is fine for batch jobs, but is trickier for interactive work through notebooks, as it leads to ridiculously low resource utilization when we can't remove idle executors. At any rate, happy to help and do some preliminary testing once you've made more progress here!

peay avatar Mar 07 '19 07:03 peay