Some profiling data (via linux-perf) for
sage: def f():
: for i in [x]range(1):
: a+a
Py2:
Samples: 26K of event 'cycles', Event count (approx.): 17630706503
Children Self Command Shared ObjectSymbol
+ 77,85%47,79% python2 libpython2.7.so.1.0
Vincent Delecroix wrote:
> Then I guess the reason of the slowdown comes from the change in
> the integer types in Python 3 and the way we handle the conversion
> from Python integers to Sage integers
This may be part of it, but I don't think it explains everything:
sage: a = 1
sage: %timeit a+a
Then I guess the reason of the slowdown comes from the change in
the integer types in Python 3 and the way we handle the conversion
from Python integers to Sage integers.
Namely we have low level mpz_set_pylong (for "long" integers) and
mpz_set_si (for machine integers, which is a GMP function).
On Saturday, November 23, 2019 at 12:38:35 PM UTC-8, vdelecroix wrote:
>
> Le 23/11/2019 à 11:34, John H Palmieri a écrit :
> > By the way, Integer(1r) is also faster with Python 2 than with Python 3.
>
> By how much? Does it explain the 25% slowdown of the original post?
>
Python 2:
sage: %
Le samedi 23 novembre 2019 20:34:51 UTC+1, John H Palmieri a écrit :
>
> It's not actually Sage 8.9 vs. 9.0, it is? Rather it's Python 2 vs. Python
> 3.
>
I confirm this: since at least Sage 8.5, Python 3 is roughly 10% slower
than Python 2 in running the manifold doctests via
sage -tp --long
Le 23/11/2019 à 11:34, John H Palmieri a écrit :
By the way, Integer(1r) is also faster with Python 2 than with Python 3.
By how much? Does it explain the 25% slowdown of the original post?
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To uns
It's not actually Sage 8.9 vs. 9.0, it is? Rather it's Python 2 vs. Python
3. On my computer, I see the same timings with Python 3 builds of 8.9 and
9.0.beta6, but things look faster with Python 2 builds of 8.9 and 9.0.beta6.
By the way, Integer(1r) is also faster with Python 2 than with Python
And could you also time compare
a = Integer(1r)
on both versions?
Le 23/11/2019 à 11:13, Marc Mezzarobba a écrit :
Vincent Delecroix wrote:
@Marc: could you perform some C profiling (it might work directly
inside Sage via %crun [2]).
Yes, I'll try to investigate a bit more, but I first
Vincent Delecroix wrote:
> @Marc: could you perform some C profiling (it might work directly
> inside Sage via %crun [2]).
Yes, I'll try to investigate a bit more, but I first wanted to ask if it
was a known issue.
--
Marc
--
You received this message because you are subscribed to the Google
This is very annoying... and should have been detected automatically.
Julian started [1] and it would be good to finish setting it up!
@Marc: could you perform some C profiling (it might work directly
inside Sage via %crun [2]).
[1] https://trac.sagemath.org/ticket/25262
[2]
http://doc.sagem
Something like object creation, memory allocation, basic arithmetic, or
cython calls seems to have become a lot slower recently.
Overall, my Python code using sage runs about 10% slower with 9.0.beta6
than with 8.9. The slowdown seems to be spread evenly across many
different functions.
But he
On Sat, 23 Nov 2019, Frédéric Chapoton wrote:
> The current stumbling point is that sagenb uses twisted and twisted is not
> py3 compatible, despite pretending to be so.
OK. I opened #28792 for better error message. Also I suppose we must
change documentation.
--
Jori Mäntysalo
Tampereen ylio
On Sat, Nov 23, 2019 at 5:10 PM Frédéric Chapoton wrote:
>
> Yes. No sagenb in Python3.
>
> The current stumbling point is that sagenb uses twisted and twisted is not
> py3 compatible, despite pretending to be so.
We are on twisted version 16, which is more than 3 years old. The
current one is 1
Yes. *No sagenb in Python3*.
The current stumbling point is that sagenb uses twisted and twisted is not
py3 compatible, despite pretending to be so.
I did make some lonely efforts to make sagenb work with py3. This stopped
on the error message that you give.
Frederic
Le samedi 23 novembre 201
Sagenb is not going to work under python3
On Sat, 23 Nov 2019, 14:13 Jori Mäntysalo (TAU),
wrote:
> I did a fresh install, i.e. start from git clone
> git://github.com/sagemath/sage.git and so on. Sage starts and I can start
> jupyter also. However ./sage --notebook=sagenb says
>
> Deprecation
I did a fresh install, i.e. start from git clone
git://github.com/sagemath/sage.git and so on. Sage starts and I can start
jupyter also. However ./sage --notebook=sagenb says
DeprecationWarning: the imp module is deprecated in favour of importlib;
see the module's documentation for alternative
Thanks for letting me know about the new options and explaining. Using
render_order one can "fix" the rendering of d5 easily enough but it seems
there is no way to do it for d1, d2, d3 and d4 in a satisfactory way upon
permutation.
sábado, 23 de Novembro de 2019 às 02:14:29 UTC, Paul Masson es
sagenb only works with Python2, so you need to run configure with the option
--with-python=2
(which used to be the default, but not any more, now 3 is the default)
On Sat, 23 Nov 2019, 09:58 João Palhoto Matos,
wrote:
> Unfortunately if you do that from inside a jupyter notebook you are unabl
Unfortunately if you do that from inside a jupyter notebook you are unable
to save the 3d model as the context menus are clipped (with sage 9.0beta6
using jsmol not jmol).
If you try to start a classical deprecated notebook it fails to start (with
sage 9.0beta6).
If you give all the commands i
19 matches
Mail list logo
