Optimise clone memory use

Bug #168637 reported by Daniel Pope
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
Confirmed
Wishlist
Unassigned

Bug Description

Clones are using a very large amount of memory.

I'm trying to construct a lawn using individual blades of grass. To do
this, I clone a blade of grass, group a bunch of clones, clone the group
and so on.

This approach requires O(log n) SVG elements to create n clones.

However, this is not observed behaviour. Inkscape memory usage appears
approximately to grow with visible blades of grass.

I expect this behaviour from duplicates which is why I'm using clones. For
clones I expect the CPU usage to be slightly higher as the clone tree is
walked on demand, but memory usage should remain low.

Tags: performance
Revision history for this message
Daniel Pope (djpope) wrote :

Originator: YES

Incidentally, grouping or ungrouping clones of groups of clones of groups
of clones takes ages.

If clones were implemented as a shallow reference rather than a deep copy
this should be instant too, shouldn't it?

Revision history for this message
Buliabyak-users (buliabyak-users) wrote :

Originator: NO

That's because most memory is taken by the renderer, not by SVG tree. This
should be much better when we switch to cairo. For now just draw it all in
outline mode (it is already cairo) and you will see memory won't grow
nearly as fast.

nightrow (jb-benoit)
Changed in inkscape:
importance: Undecided → Wishlist
status: New → Confirmed
tags: added: performance
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.