Re: [sage-devel] Re: Parallel computing

2015-10-04 Thread William Stein
On Sunday, October 4, 2015, Jori Mäntysalo wrote: > On Sun, 4 Oct 2015, William Stein wrote: > > If I am right, there is no EASY parallel functions in Sage. >>> >> >> Type >> >> parallel? >> >> in Sage for a simple but very useful parallel decorator in Sage, that >> I addedabout 6 years. The A

Re: [sage-devel] Re: Parallel computing

2015-10-04 Thread Jori Mäntysalo
On Sun, 4 Oct 2015, William Stein wrote: If I am right, there is no EASY parallel functions in Sage. Type parallel? in Sage for a simple but very useful parallel decorator in Sage, that I addedabout 6 years. The API is slightly confusing, and it would be nice to have something better. But

Re: [sage-devel] Re: Parallel computing

2015-10-04 Thread William Stein
On Sun, Oct 4, 2015 at 10:29 PM, Jori Mäntysalo wrote: > Just a stupid side-question: > > On Sun, 4 Oct 2015, Victor Shoup wrote: > >> Also, now that NTL is threadsafe, I'm looking at making some of the >> low-level routines thread enhanced. > > >> For up to 4 threads, I get close to linear speedu

Re: [sage-devel] Re: Parallel computing

2015-10-04 Thread David Roe
On Mon, Oct 5, 2015 at 2:29 PM, Jori Mäntysalo wrote: > Just a stupid side-question: > > On Sun, 4 Oct 2015, Victor Shoup wrote: > > Also, now that NTL is threadsafe, I'm looking at making some of the >> low-level routines thread enhanced. >> > > For up to 4 threads, I get close to linear speedup

Re: [sage-devel] Please please revert the recent changes to the docbuilder!

2015-10-04 Thread Jori Mäntysalo
On Sun, 4 Oct 2015, Simon King wrote: Since a couple of weeks, building Sage becomes really annoying. "make start" is fine. But as soon as I want to build the docs in two parallel threads, it makes my laptop unusable because of swapping. Was this an exact description? I have noticed that buil

[sage-devel] Re: Parallel computing

2015-10-04 Thread Jori Mäntysalo
Just a stupid side-question: On Sun, 4 Oct 2015, Victor Shoup wrote: Also, now that NTL is threadsafe, I'm looking at making some of the low-level routines thread enhanced. For up to 4 threads, I get close to linear speedup...but after that, it starts to degrade: at 16 threads I only get 8x

[sage-devel] Re: FLINT/NTL benchmarks

2015-10-04 Thread Victor Shoup
Thanks for the feedback, Bill! A bit of friendly competition is always a good thing :-) I've been looking into SIMD for small prime FFT's...unfortunately, there is currently no CPU out there that supports SIMD 64x64 -> high order 64 bits of product. So, it does not look very promising. In a cou

[sage-devel] Re: FLINT/NTL benchmarks

2015-10-04 Thread Bill Hart
In particular it really looks like we should study the factorisation algorithms in NTL, since the performance you have there seems unlikely to be explained by mere arithmetic performance. We are likely missing a number of tricks. Bill. On Monday, 5 October 2015 02:06:26 UTC+2, Bill Hart wrote:

[sage-devel] Re: FLINT/NTL benchmarks

2015-10-04 Thread Bill Hart
This is really nice Victor. Thanks for sharing these benchmarks! There are two things we really need to do in Flint fairly soon: 1) make better use of SIMD (e.g. small primes FFT is now probably competitive with our Schoenhage-Strassen FFT) and 2) make use of threading. Flint is actually starti

[sage-devel] FLINT/NTL benchmarks

2015-10-04 Thread Victor Shoup
I've recently done some benchmarking to compare FLINT and NTL. I've tried to be as fair as possible in the comparisons. If anyone is interested, you can see the results here: http://shoup.net/ntl/benchmarks.pdf The upshot is: FLINT is faster for some things, and NTL is faster for other things.

[sage-devel] Re: Please please revert the recent changes to the docbuilder!

2015-10-04 Thread Simon King
Am Montag, 5. Oktober 2015 00:44:00 UTC+2 schrieb Volker Braun: > > See > https://groups.google.com/forum/#!msg/sage-release/MGkb_-y-moM/j0qABCAKBAAJ > > What version was OK for you? > Difficult to tell. I had the impression that it gradually became worse in the past year or so, becoming reall

[sage-devel] Re: Please please revert the recent changes to the docbuilder!

2015-10-04 Thread Volker Braun
See https://groups.google.com/forum/#!msg/sage-release/MGkb_-y-moM/j0qABCAKBAAJ What version was OK for you? On Sunday, October 4, 2015 at 11:22:06 PM UTC+2, Simon King wrote: > > Hi! > > Since a couple of weeks, building Sage becomes really annoying. "make > start" is fine. But as soon as I wa

Re: [sage-devel] How to declare dependencies of new-style packages?

2015-10-04 Thread John Cremona
On 4 October 2015 at 17:00, Simon King wrote: > Hi! > > Am Sonntag, 4. Oktober 2015 22:34:38 UTC+2 schrieb Snark: >> >> If MEATAE isn't defined, you add a depend on $(INST)/, which does exist, >> so >> it's an always-satisfied dep and not an error, isn't it? > > > I am confused. Do you say that FO

[sage-devel] Please please revert the recent changes to the docbuilder!

2015-10-04 Thread Simon King
Hi! Since a couple of weeks, building Sage becomes really annoying. "make start" is fine. But as soon as I want to build the docs in two parallel threads, it makes my laptop unusable because of swapping. Is there really a good reason why one should now use so much more memory than in the past?

Re: [sage-devel] How to declare dependencies of new-style packages?

2015-10-04 Thread Simon King
Hi! Am Sonntag, 4. Oktober 2015 22:34:38 UTC+2 schrieb Snark: > > If MEATAE isn't defined, you add a depend on $(INST)/, which does exist, > so > it's an always-satisfied dep and not an error, isn't it? > I am confused. Do you say that FOO is defined regardless whether the optional package fo

Re: [sage-devel] How to declare dependencies of new-style packages?

2015-10-04 Thread Simon King
Hi! Am Sonntag, 4. Oktober 2015 22:34:38 UTC+2 schrieb Snark: > > If MEATAE isn't defined, you add a depend on $(INST)/, which does exist, > so > it's an always-satisfied dep and not an error, isn't it? > I am confused. Do you say that FOO is defined regardless whether the optional package fo

Re: [sage-devel] How to declare dependencies of new-style packages?

2015-10-04 Thread Jeroen Demeyer
On 2015-10-04 22:31, Simon King wrote: OK. But what should happen, if I replace it with $(INST)/$(MEATAE) ? Shouldn't it fail with an error? Well, it didn't (which was a bug, IMHO) OK, I agree that this is annoying and I am aware of that. But let's live with it for a moment. There have been a lo

Re: [sage-devel] How to declare dependencies of new-style packages?

2015-10-04 Thread Julien Puydt
Le dimanche 04 oct. 2015 à 13:31:19 (-0700), Simon King a écrit : > > OK. But what should happen, if I replace it with $(INST)/$(MEATAE) ? > Shouldn't it fail with an error? Well, it didn't (which was a bug, IMHO), > at least on a branch that was not very old. Hopefully the latest develop > wor

Re: [sage-devel] How to declare dependencies of new-style packages?

2015-10-04 Thread Simon King
Hi Jeroen, Am Sonntag, 4. Oktober 2015 22:20:03 UTC+2 schrieb Jeroen Demeyer: > > On 2015-10-04 19:27, Simon King wrote: > > In the developer manual I couldn't find a syntax definition for the > > "dependencies" file. > Did you look in the *most recent* version of the developer's manual? I > m

Re: [sage-devel] How to declare dependencies of new-style packages?

2015-10-04 Thread Jeroen Demeyer
On 2015-10-04 19:27, Simon King wrote: In the developer manual I couldn't find a syntax definition for the "dependencies" file. Did you look in the *most recent* version of the developer's manual? I mean not the one which is online but the one in your local develop branch. Suppose I want that

Re: [sage-devel] Re: How to declare dependencies of new-style packages?

2015-10-04 Thread Jeroen Demeyer
On 2015-10-04 21:55, Simon King wrote: If I misspell the name of the dependency of my package on purpose, then the package still installs Well, don't misspell :-) -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and

[sage-devel] Re: How to declare dependencies of new-style packages?

2015-10-04 Thread Simon King
Am Sonntag, 4. Oktober 2015 21:21:58 UTC+2 schrieb Simon King: > > > I don't see the developer manual mentioning the meaning of $(INST); I can > only guess that it is a command that installs another package unless it is > installed already. But what package? Do you confirm my guess that > $(INS

[sage-devel] Re: How to declare dependencies of new-style packages?

2015-10-04 Thread Simon King
And PS: Will the user be asked for confirmation if the dependency's license is not GPL compatible (as is the case for database_gap)? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it

[sage-devel] Re: How to declare dependencies of new-style packages?

2015-10-04 Thread Simon King
Hi Volker, Am Sonntag, 4. Oktober 2015 20:54:25 UTC+2 schrieb Volker Braun: > > Its makefile syntax since its really just a script that glues everything > together into one makefile. The ones after the pipe are order only > dependencies. > > I don't see the developer manual mentioning the meani

[sage-devel] Re: How to declare dependencies of new-style packages?

2015-10-04 Thread Volker Braun
Its makefile syntax since its really just a script that glues everything together into one makefile. The ones after the pipe are order only dependencies. On Sunday, October 4, 2015 at 7:27:48 PM UTC+2, Simon King wrote: > > Hi! > > Meanwhile I try to change my group cohomology spkg into a new

[sage-devel] How to declare dependencies of new-style packages?

2015-10-04 Thread Simon King
Hi! Meanwhile I try to change my group cohomology spkg into a new style package. But I wonder how dependencies are checked these days. I see, for example, the file build/pkgs/cvxopt/dependencies: $(INST)/$(NUMPY) $(INST)/$(ATLAS) $(INST)/$(CEPHES) $(INST)/$(GSL) $(INST)/$(GLPK) | $(INST)/$(MATP

[sage-devel] threejs

2015-10-04 Thread Thierry Dumont
What about the optional package threejs ? As far as I remember, the idea was to replace jmol with it. (But may be I am wrong). Is this always an active project? Is it an orphan project ? Are there difficult problems to solve ? t.d. -- You received this message because you are subscribed to

Re: [sage-devel] History of notebooks.

2015-10-04 Thread Thierry Dumont
William, Thank you for this detailed answer! For my talk to the group of engineers I mentioned, it is more than perfect. But I am also involved a bit in the history of computing: I think we must keep track of the different developments and writing history without such documents is very difficu