Same as
https://ask.sagemath.org/question/65840/bugged-interaction-with-signal-handler-sagemath-95-linux/
This is a minimal reproducible example of a bug using a typical interrupt
handler so that files being written to are not corrupted. Running the
script as `python filename.py` works as inten
Hi all,
we recently noticed that the IntegerMatrix class from fpylll is (on our
hardware) much slower in sage9.x, than it is in sage8.x.
Please consider the following code snippet:
import time
from fpylll import IntegerMatrix
dim = 30
bits = 10
A = IntegerMatrix.random( dim, "uniform", bits =
Hi there,
I don’t think A*B is a good benchmark for FPyLLL does the same slowdown also
appear for, say, LLL?
Cheers,
Martin
On Tue, Jan 10 2023, 'Julian Nowakowski' via sage-devel wrote:
> Hi all,
>
> we recently noticed that the IntegerMatrix class from fpylll is (on our
> hardware) much slow
Hi Martin,
the slowdown also appears in other contexts. In particular, it also appears
when running LLL.
Running the following code on our machine takes approximately 1 second with
sage 8.1 and 8.9, but approximately 10 seconds with sage 9.3 and 9.7.
import time
from fpylll import IntegerMatrix
This does not appear to be Sage-related.
You can run the code above in Python shell.
(e.g. you can start Sage's python as "sage --python")
HTH
Dima
On Tue, Jan 10, 2023 at 3:48 PM 'Julian Nowakowski' via sage-devel
wrote:
>
> Hi Martin,
>
> the slowdown also appears in other contexts. In particu
Dear Sage developers,
One of the first things we do when we create a new ticket is to choose the
"Component" for which the ticket is. After we move to GitHub, we instead
would choose a label of the form "component: ...". Like in Trac, the kind
of labels will rarely change and you will be forced
