> The point is to avoid the python overhead in calling the add/delete
> functions. So yes, you would need to write your calls to the cython
> add/delete functions in Cython.
A simple example in the notebook:
%cython
from sage.graphs.base.c_graph cimport CGraph
from sage.all import graphs
G = gra
On 5/14/10 2:31 PM, Ryan Hinton wrote:
On May 14, 1:54 pm, Jason Grout wrote:
Are you adding/deleting things using the python functions, or are you
using the Cython interface to the underlying CGraph structure? If you
are using python, you can probably speed up these operations by 100x or so.
On May 14, 1:54 pm, Jason Grout wrote:
> Are you adding/deleting things using the python functions, or are you
> using the Cython interface to the underlying CGraph structure? If you
> are using python, you can probably speed up these operations by 100x or so.
My code is straight Python. To us
Just in case, because I do not know enough the C backends to give you
a useful answer (watch out for Robert Miller !) :
Did you try to specify to use a Dense backend, if your graph is not
too large ?
Nathann
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe f
On 5/14/10 12:48 PM, Ryan Hinton wrote:
I am running some Monte Carlo simulations where I construct and pull
apart graphs. If I can get them to run faster, I can get my results
faster or with higher precision/confidence.
I can give details if desired, but most of the processor time is spent
in
