tgravescs commented on PR #34622:
URL: https://github.com/apache/spark/pull/34622#issuecomment-1587859613
yeah I believe I was implementing similar functionality in a tool we have
and that algorithm had performance issues when things got large. I'll have to
go dig it up again though.
tgravescs commented on PR #34622:
URL: https://github.com/apache/spark/pull/34622#issuecomment-1583262505
sure, its been a while but I think I had tried this out and was seeing some
performance issues with it. I'd have to relook at it to remember. Did you run
any performance tests?
--
tgravescs commented on PR #34622:
URL: https://github.com/apache/spark/pull/34622#issuecomment-1088731095
sorry, I missed your response.
After looking some more the list of jobs can get very long as well. I'm
fine with leaving the list of stages as well.
Do you know how long
tgravescs commented on pull request #34622:
URL: https://github.com/apache/spark/pull/34622#issuecomment-1063288915
So a couple questions and concerns.
1. I'm not sure having the list of Completed Stages at the top of the page
helps and I'm concerned that could be a very long list.
tgravescs commented on pull request #34622:
URL: https://github.com/apache/spark/pull/34622#issuecomment-976749417
yes, it would be nice to have the actual stagIds in the ui, I'll need to
look closer at the logic though, which likely won't be til next week.
--
This is an automated
