Re: [sage-devel] Massive slowdown in ring inverses

2015-01-28 Thread Nils Bruin
On Monday, January 26, 2015 at 4:30:38 PM UTC-8, vdelecroix wrote: > > Trying (line 59):TestSuite(M).run() # long time (52s on sage.math, > 2012) > Expecting nothing > ok [141.39 s] > Doing "%prun TestSuite(M).run()" gives 2311224 function calls (2306683 primitive calls) in 156

Re: [sage-devel] Massive slowdown in ring inverses

2015-01-27 Thread Nils Bruin
On Tuesday, January 27, 2015 at 10:05:02 AM UTC-8, vdelecroix wrote: > > Interesting. Note that the :2 () part actually comes > from hashing... Why do you think that? According to the profiling, this gets called only once, has a modest "total" time and a large variation in the "cumulative". I

Re: [sage-devel] Massive slowdown in ring inverses

2015-01-27 Thread Vincent Delecroix
Interesting. Note that the :2 () part actually comes from hashing... as hash is defined by the wonderful def __hash__(self): return hash(str(self)) I am not so sure why there is much more call to has than before. Vincent 2015-01-27 18:23 UTC+01:00, Stefan : > I ran the same code wit

Re: [sage-devel] Massive slowdown in ring inverses

2015-01-27 Thread Stefan
I ran the same code with cProfile. Here's the output: perron:sage5 svanzwam$ ./sage/sage speedtest.sage Sage Version 5.12, Release Date: 2013-10-07 (0, 3, 1, 0, 2, 1) 7193816 function calls (7193814 primitive calls) in 3.425 seconds Ordered by: standard name ncalls tottime perca

Re: [sage-devel] Massive slowdown in ring inverses

2015-01-26 Thread Vincent Delecroix
Hello, Not sure whether it is related or not. In the file sage/rings/function_field/function_field.py there are two doctests that take respectively much shorter and much longer than what is written. Namely Trying (line 58):TestSuite(L).run() # long time (8s on sage.math, 2012) Expecting noth