1 | initial version |

Note that Sage relies on other systems for its computations. For examples, matrices over `RDF`

are handled by `openblas`

, matrices over `ZZ`

are handled by `flint`

. So, in each case, we should see if there are compilaton options that allow that system to use all your cores. It will also depend on the method used, since some algorithms are more parallelisable than others. Hence, to provide a meanongful answr, it is necessary to know:

If `M`

is your matrix, what is the answer of:

```
sage: parent(M)
sage: type(M)
```

and what are the methods that you want to run intensively ?

Note that, in the tests i just quickly did, while i am compiling Sage, i could only see one core work in various situations with various backends. But it does not means that there is nothing to do, it might be possible to allow some parallelism at compulation time.

2 | No.2 Revision |

Note that Sage relies on other systems for its computations. For ~~examples, ~~example, matrices over `RDF`

are handled by `openblas`

, matrices over `ZZ`

are handled by `flint`

. So, in each case, we should see if there are compilaton options that allow that system to use all your cores. It will also depend on the method used, since some algorithms are more parallelisable than others. Hence, to provide a ~~meanongful ~~meaningful answr, it is necessary to know:

If `M`

is your matrix, what is the answer of:

```
sage: parent(M)
sage: type(M)
```

and what are the methods that you want to run intensively ?

Note that, in the tests i just quickly did, while i am compiling Sage, i could only see one core work in various situations with various backends. But it does not means that there is nothing to do, it might be possible to allow some parallelism at compulation time.

Copyright Sage, 2010. Some rights reserved under creative commons license. Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.