-
-
Notifications
You must be signed in to change notification settings - Fork 453
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
Remove unnecessary signal handling for low prec mpfr operations. #7879
Comments
comment:1
Signal handling is omitted for functions/precisions that were clearly and uniformly in the millisecond range or less. |
This comment has been minimized.
This comment has been minimized.
Attachment: 7879-RR-signal.patch.gz |
Reviewer: Alex Ghitza |
Author: Robert Bradshaw |
comment:3
This looks good. I have one question: you are hardcoding threshold precisions after which the signals should be used, mostly 1000, but also 10000 in a couple of places. Would it be better to have a global variable PREC_THRESHOLD set to 1000 at the top of the file, and then use it or 10*PREC_THRESHOLD where needed? It would make it easier to change this in the future, since a search for it would be all that's needed. I'm marking this as needs_info. If you think it's not worth the trouble, I'll put a positive review. |
comment:4
I am proposing to close this ticket as invalid since #9678 makes |
comment:5
Since this ticket is marked sage-duplicate/invalid/wontfix plus has |
comment:6
Robert, what is your opinion? |
comment:7
Thanks for taking a look at this. I've been waiting for 4.7 to be released to re-base this, and think it'd still worth having. Perhaps I'll put PREC_THRESHOLD in there while I'm at it, and maybe do some benchmarking. |
comment:9
Replying to @robertwb:
If you find useful ways to do benchmarks, please let me know. I might re-use those benchmarks to optimize |
comment:10
The patch adds one unrelated doctest. This doctest has been moved to #11344. |
comment:11
Looks like about a 5% win (much smaller than I remember it being before). |
Attachment: 7879-RR-signal.2.patch.gz Rebased on 4.7 |
comment:12
patch attachment: 7879-RR-signal.2.patch applied to sage-4.7.1.alpha1. Then did 'sage -b' followed by 'make testlong'.
etc. |
comment:13
Replying to @sagetrac-mariah:
These errors don't occur for me with sage-4.7.2.alpha2. |
Changed reviewer from Alex Ghitza to Alex Ghitza, William Stein |
comment:14
I did a full test of Sage on another machine too with 4.7.2.alpha2, and everything works. Code looks good and addresses other people's issues... |
Changed keywords from none to sd32 |
This comment has been minimized.
This comment has been minimized.
Changed reviewer from Alex Ghitza, William Stein to Alex Ghitza, Mariah Lenox, William Stein |
Sage library patch. Robert's patch rebased to Sage 4.7.2.alpha2, because of fuzz 2. |
Attachment: trac_7879-RR-signal.2.rebased_to_4.7.2.alpha2.patch.gz Attachment: trac_7879-harmless_fuzz_2.diff.gz Do not apply. Fuzz against Sage 4.7.2.alpha2. For reference only. |
This comment has been minimized.
This comment has been minimized.
comment:17
Attached a rebased patch because of fuzz. |
Merged: sage-4.7.2.alpha3 |
_sig_on
and_sig_off
are more expensive than computing the result itself.Apply only attachment: trac_7879-RR-signal.2.rebased_to_4.7.2.alpha2.patch to the Sage library.
Component: basic arithmetic
Keywords: sd32
Author: Robert Bradshaw
Reviewer: Alex Ghitza, Mariah Lenox, William Stein
Merged: sage-4.7.2.alpha3
Issue created by migration from https://trac.sagemath.org/ticket/7879
The text was updated successfully, but these errors were encountered: