[sage-devel] a 7(!) year old (Singular) overflow issue still holds

https://trac.sagemath.org/ticket/6472 even for recent singular upgrade https://trac.sagemath.org/ticket/17254 and it was not(?) reported to upstream... -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this grou

Re: [sage-devel] multithreading performance issues

I've done a few more tests finding bad performance (and some decent improvements with a few threads). Also, I double checked that the default behavior for me seems to be the same as setting OMP_NUM_THREADS=64. I wonder if others who have a recent development version of Sage see similar results. I'm

Re: [sage-devel] Re: slow doctest number_field_element.pyx on my machine

I'm not confident that there is no issue, maybe I could take a look. I suspect that the implementation is optimized for or runs best on specific harware/environment, which is not a priori bad. In addition I think that REALLY GOOD TIMING TESTS will need some extra effort, namely: (multiple) (com

Re: [sage-devel] multithreading performance issues

On Tue, Oct 4, 2016 at 9:03 PM, William Stein wrote: > On Tue, Oct 4, 2016 at 12:58 PM, Jonathan Bober wrote: > > No, in 7.3 Sage isn't multithreading in this example: > > > > jb12407@lmfdb1:~$ sage73 > > sage: %time M = ModularSymbols(5113, 2, -1) > > CPU times: user 599 ms, sys: 25 ms, total:

Re: [sage-devel] Re: slow doctest number_field_element.pyx on my machine

On Tue, Oct 04, 2016 at 01:13:49PM -0700, Volker Braun wrote: > I've seen that time out often on the buildbot, too. Please, somebody > replace the test in there by something more reasonable. Just to be sure, are you confident that this is not pointing some issue ? Ciao, Thierry > > On Tuesday

[sage-devel] Re: slow doctest number_field_element.pyx on my machine

I've seen that time out often on the buildbot, too. Please, somebody replace the test in there by something more reasonable. On Tuesday, October 4, 2016 at 9:53:13 PM UTC+2, Jakob Kroeker wrote: > > on my machine (fedora 23, 32 Bit) the test > > sage -t --long --warn-long 127.3 src/sage/rings/n

Re: [sage-devel] slow doctest number_field_element.pyx on my machine

Hi, for what it worth, i have the same issue on my 32bit build VM (running Debian jessie). Ciao, Thierry On Tue, Oct 04, 2016 at 12:53:13PM -0700, Jakob Kroeker wrote: > on my machine (fedora 23, 32 Bit) the test > > sage -t --long --warn-long 127.3 src/sage/rings/number_field/ > number_field

Re: [sage-devel] multithreading performance issues

On Tue, Oct 4, 2016 at 12:58 PM, Jonathan Bober wrote: > No, in 7.3 Sage isn't multithreading in this example: > > jb12407@lmfdb1:~$ sage73 > sage: %time M = ModularSymbols(5113, 2, -1) > CPU times: user 599 ms, sys: 25 ms, total: 624 ms > Wall time: 612 ms > sage: %time S = M.cuspidal_subspace().

[sage-devel] slow doctest number_field_element.pyx on my machine

on my machine (fedora 23, 32 Bit) the test sage -t --long --warn-long 127.3 src/sage/rings/number_field/ number_field_element.pyx takes 1397.8 seconds (10 times more) And thus the patchbot test run for sage 7.4.beta6 fails I have aIntel(R) Core(TM)2 Duo CPU E8200 @ 2.66GHz ; it shou

Re: [sage-devel] multithreading performance issues

No, in 7.3 Sage isn't multithreading in this example: jb12407@lmfdb1:~$ sage73 sage: %time M = ModularSymbols(5113, 2, -1) CPU times: user 599 ms, sys: 25 ms, total: 624 ms Wall time: 612 ms sage: %time S = M.cuspidal_subspace().new_subspace() CPU times: user 1.32 s, sys: 89 ms, total: 1.41 s Wall

Re: [sage-devel] multithreading performance issues

openmp is disabled in linbox/ffpack-fflas so it must come from somewhere else. Only R seems to be linked to libgomp (openmp) on my vanilla install. Curiosity: do you observe the same behaviour in 7.3? François > On 5/10/2016, at 07:26, Jonathan Bober wrote: > > See the following timings: If I s

[sage-devel] multithreading performance issues

See the following timings: If I start Sage with OMP_NUM_THREADS=1, a particular computation takes 1.52 cpu seconds and 1.56 wall seconds. The same computation without OMP_NUM_THREADS set takes 12.8 cpu seconds and 1.69 wall seconds. This is particularly devastating when I'm running with @parallel

Re: [sage-devel] hash of QQbar inefficient

Hi, without exploring deeply, it looks like an unlucky collision with the shift by the particular QQbar_hash_offset=1/987654321*I+1/123456789 (which aims to avoid collisions for more usual algebraic numbers like 1 or 2). sage: from sage.rings.qqbar import QQbar_hash_offset sage: QQbar_hash_offset

[sage-devel] hash of QQbar inefficient

Hashing of QQbar elements seems to be quite inefficient: sage: R. = AA[] sage: rho = QQbar.polynomial_root( : x^5 - 1/3*x^4 + 1/30*x^3 - 1/600*x^2 + 1/24000*x - 1/240, : CIF(RIF(0.02, 0.03), RIF(-0.009, -0.007))) sage: %time hash(rho) CPU times: user 14 s, sys: 36 ms, total: 14

[sage-devel] Trac #21252 - Nonlinear Invariants of an S-Box

Hi everyone, I would appreciate if someone could step-in and review ticket #21252 . Its an implementation of computing nonlinear invariants of an S-Box, which is a part of a newly proposed cryptanalytic techniques in http://eprint.iacr.org/2016/732.pdf. Bes

Re: [sage-devel] State of sage built with clang/clang++ on OS X - update

> On 4/10/2016, at 20:39, Ralf Stephan wrote: > > Ah that would be a wrong libffi-devel version on OpenSuSE, shouldn't > this be tested by Sage configure? > That would explain. Note that I only tested the odd package on linux and most of what I have done has been on OS X. So there definitely c

Re: [sage-devel] State of sage built with clang/clang++ on OS X - update

Ah that would be a wrong libffi-devel version on OpenSuSE, shouldn't this be tested by Sage configure? Now I get this: [libgap-4.8.3] /usr/lib64/gcc/x86_64-suse-linux/4.8/../../../../x86_64-suse-linu x/bin/ld: .libs/libgap_la-ariths.o: relocation R_X86_64_32S against `libGAP_ZERO Op' can not be

Re: [sage-devel] State of sage built with clang/clang++ on OS X - update

I cannot find mention of ecl problems: [ecl-16.1.2.p2] /home/ralf/sage/local/var/tmp/sage/build/ecl-16.1.2.p2/src/src/c/ffi.d:148:44: error: use of undeclared identifier 'FFI_SYSV' [ecl-16.1.2.p2] {((cl_object)(cl_symbols+(1604))), FFI_SYSV}, [ecl-16.1.2.p2]