The dense multicore examples will take months to run in Flint, since we
haven't written the code yet! :-)
But your explanation about the cost of conversion in the sparse case
certainly more than accounts for overall difference in performance.
Giac also has a symbolic front end, too, which
Now that you have given the precise conditions, I will check if they are
equivalent to whats in the smp code. They do look like what I was aiming
for.
As for caching the last entry, that code is still in there in a thread-safe
way. This optimisation had no effect on the timings when the
Le mardi 26 septembre 2017 10:43:10 UTC+2, Bill Hart a écrit :
>
> We used to do this, and Daniel noticed that it wasn't really threadsafe.
>
It would be in my implementation, but inserting requires sometimes memory
allocation and it seems to slow down too much. Anyway, as explained
earlier,
We used to do this, and Daniel noticed that it wasn't really threadsafe. I
don't know the current status of this. At some point he said it didn't make
any difference after he got the delayed insertion working.
I didn't check carefully, but maybe he stores it in the final heap location
now. But
Roman Pearce said he would put up some code to explain this. (The
conditions Daniel uses are quite complex in comparison.) I therefore think
that it's ok to quote the following from correspondence with Roman (since I
put up my blog):
[The idea is based on ] "Ellis Horowitz, A Sorting Algorithm
I found a way to get better timings by caching the index of the insertion
chain of the previous monomial. But now multi-threaded execution is slower
than 1 thread execution most certainly because of locks during insertion...
I will probably force 1 thread sparse multiplication.
--
You
Le lundi 25 septembre 2017 18:56:26 UTC+2, Bill Hart a écrit :
>
> Do you use anything special for memory management? Mickael Gastineau
> recommended jemalloc, which we haven't tried yet. I assume you expected to
> see better times for the threaded benchmarks with giac?
>
I'm not using
Do you use anything special for memory management? Mickael Gastineau
recommended jemalloc, which we haven't tried yet. I assume you expected to
see better times for the threaded benchmarks with giac? We've had to work
way too hard to get good timings for this. But we see the same issues on
On the main benchmark machine we have gcc-4.8.4.
On Monday, 25 September 2017 12:32:39 UTC+2, parisse wrote:
>
> Hi,
>
> Which compiler are you running?
>
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop
Hi,
Which compiler are you running?
--
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, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to
10 matches
Mail list logo
