[uDraw(Graph)-Users] (no subject)

[Pieter Bellens]

Hi,


i ve been playing around with UDrawGraph for some time now, mainly for
representing annotated direct acycling graphs. The graph itself is
generated by another program, and piped to UDG using the variety of
string commands from the API. When drawing larger graphs (e.g. 200
nodes, 600 edges) UDG slows down tremendously, taking on average 2
seconds to refresh the window after each update. Also, i observe a
processor usage of  +95%, and a pretty big memory footprint (almost 30Mb). 
My application repeatedly adds one node, or a collection of edges, to
the graph. Pretty much in one burst, sending a few thousand of these
operations to UDG through the pipe in a matter of seconds.   

Has anybody else observed this behaviour, and maybe found a remedy for
it? Would it help if i decrease the number of communications, in favor
of bigger updates (more nodes and edges in a single piped message)? Or
is UDG simply not fit for larger graphs?



thanks in advance,



pieter bellens