-
-
Notifications
You must be signed in to change notification settings - Fork 720
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Start uncythonization #6104
Start uncythonization #6104
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What remains to be done after this?
@property | ||
def duration(self) -> double: | ||
return self._duration |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Losing these properties makes me very happy 😄
Unit Test Results 16 files ± 0 16 suites ±0 7h 21m 27s ⏱️ - 17m 10s For more details on these failures, see this check. Results for commit 850f0df. ± Comparison against base commit bd3f47e. ♻️ This comment has been updated with latest results. |
@mrocklin , added update to the description. Currently all tests in test_scheduler.py pass bar one. Of course, it would be nice to push this through quickly, else it'll cause major merge conflicts. |
(now all tests in test_scheduler pass; but there are more tests in general which I haven't even tried yet, and of course appeasing mypy) |
Thank you for your effort here. I agree with the need to squeeze this in.
…On Tue, Apr 12, 2022 at 1:33 PM Martin Durant ***@***.***> wrote:
(now all tests in test_scheduler pass; but there are more tests in general
which I haven't even tried yet, and of course appeasing mypy)
—
Reply to this email directly, view it on GitHub
<#6104 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACKZTC3JCYI67OBA5E4YSDVEW6XRANCNFSM5TEHAH4Q>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Thanks for working on this Martin! |
Maybe we should close these issues/PRs as well?
Also maybe this one? |
Also would be good to revert PR ( #5831 ) |
bahh yeah, I hope there's no too much of that |
Shouldn't be, but please let me know if you run into issues. Would be tempted to just try |
@charlesbluca, could you please look at the Conda package changes here to make sure we haven't missed anything? |
Some green! :) |
Would anyone here like to help me mypy this out? See the last bullet of the description. |
Remove distributed-impl from distributed recipe
OK, just types left. Who votes for liberal "ignore" to move forward versus those for sprinkling types around? |
Personally am ok with that approach 👍 |
Can you say more about what you mean about having "types left"? Is this mypy complaining to you, or are there still cython types lying around? Also, just to clarify on scope, full decythonization (which I don't think you're on the hook for, to be clear) would also involve rejoining things like SchedulerState, decide_worker, and so on. There were a variety of code structure changes that were done to accomdate Cython which we would probably want to undo. (although again, you're not on the hook for this solo) |
I meant mypy - the reason that the lint CI run shows red. I have fixed some locally, we'll see how far I get tonight. I'm not sure why they weren't picked up before.
Yes, agreed, all the changes I want to make in this PR are ready except mypy types. Actually, I thought it could do with some thinking about whether we want to remerge the classes or not - to be had in a separate discussion. |
Down to 16 missing type annotations and no errors |
I'm fine with liberal use of |
General comments
|
Right got the sense that the reason Coiled requested dropping Cythonization is that there is other work Coiled wants to pursue in the Scheduler. Assuming I've understood this correctly (which I may not, please feel free to correct me), it seems like we should decide on a handoff point. It seems like Martin has done a great job at dropping Cython already. So think we are very close to (if not already at) this handoff point. |
Co-authored-by: crusaderky <crusaderky@gmail.com>
Co-authored-by: crusaderky <crusaderky@gmail.com>
Co-authored-by: crusaderky <crusaderky@gmail.com>
OK, I'll reinstate them in a later PR.
I agree they should be dealt with at a later stage. |
Not quite. We've identified that the main bottleneck to use today isn't performance, but rather stability. We're not really doing anything new these days. We're mostly trying to keep the lights on (fight deadlocks, get CI working again, figure out how to keep memory under control, and so on). There was significant complexity accrued in the Cythonization effort without really providing a ton of value for a while, and so we're arguing to drop it. That's ok, not every experiment needs to succeed. Mostly I want to avoid the impression that there is some secret work happening somewhere for which this is required. We're in full maintenance mode right now. Help on that maintenance is welcome, especially from folks who know a lot about what happened in this experiment. We can take all of of the maintenance though if other folks are too busy. |
No worries. Did not have that impression. Florian had mentioned in one of our calls doing similar cleanup with the Scheduler as is being done with the Worker. So this is what I was thinking of here. Don't really know what that would entail so was sparse in details in my previous comment. |
All good, @crusaderky ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ready to merge as soon as CI is green
Thank you |
Notes:
most underscored attributes with property attributes have been replaced by simple non-underscored attributes, since they were non-uniformly accessed using both modes; a few need actions on set, so those have been maintained. This change may even improve performance slightly for fewer name lookups.
attributes of the Scheduler and underscored methods have not been changed
the class hierarchy has not been reverted yet, and I am not convinced we need to
we have lost some type information, which was mostly in the form of cython types; mypy complains a lot (but how did it ever pass??). Existing types are inconsistent in a number of places, since
__init__
s set aNone
value and this is immediately overwritten at the site of instance creation, e.g.,.prefix
innew_task()
.Closes Cythonized Builds community#228 , Extract SchedulerState from Scheduler #5839 , we had a community issue about this?
Tests added / passed
Passes
pre-commit run --all-files