In this particular instance there aren't any objects with 'lots' of nodes.

I'm attaching a design where the performance issued are less severe
than the one I'm experiencing with a design I cannot share, although
the complexity of the latter is not that much greater. They are both
generated by the same software, so should exhibit similar 'symptoms'.
Things get clunky when zoomed in and after a while of editing and
zooming in and out. Hiding layers doesn't seem to make much
difference. Maybe this could shed some light on the issue?

Thanks,
Saar.



On Mon, Mar 21, 2016 at 11:49 AM, C R <cajhne@...400...> wrote:

I decided to quickly stress test this, making a 100 point star, replicating
it 50 times, converting the objects to geometry, then shrinking them all
down to .5mm and zooming to 12800%

Result: There is some slowdown, but not nearly as much as I was expecting.
This is on a 4 year old laptop running Ubuntu Linux with Gnome 3.

What does slow it down a lot more however is taking those 50 objects, and
ctrl-k converting them to a single object. The slowdown is approximately 10x
slower than what it was before.

If this is what's slowing you down, my advice would be to break your large
(in number of points) object up into multiple objects while editing, then
recombine them when done.

ctrl-shift-k to break apart, and ctrl+k to recombine.

-C





On Mon, Mar 21, 2016 at 11:31 AM, Saar Drimer <saar@...3359...> wrote:

OK - Does removing transperance completely speed things up?

Just tried by removing all opacity. Doesn't make a difference.

Thanks,
Saar.



On Mon, Mar 21, 2016 at 9:47 AM, Olof Bjarnason
<olof.bjarnason@...400...> wrote:

OK - Does removing transperance completely speed things up?



Mvh


/Olof
-----------------
3-5-åriga småttingar i närheten?
Lek & lär siffror och bokstäver via mobilen m.h.a. Alfamem till Android.
https://play.google.com/store/search?q=alfamem


On 21 March 2016 at 10:43, Saar Drimer <saar@...3359...> wrote:

Hello Olof,

The entire file has no effects (hence going to 'fastest' in the
settings has no effect), no patterns, and no blur. Most elements do,
however, have some degree of transparency.

Thanks,
Saar.




On Mon, Mar 21, 2016 at 9:34 AM, Olof Bjarnason
<olof.bjarnason@...400...> wrote:

Are you using any effects on the paths, e.g. bitmap patterns, blur /
transparency or other?

I have also experienced severe performance problems when zooming in
paths
with bitmap patterns on them.



Mvh


/Olof
-----------------
3-5-åriga småttingar i närheten?
Lek & lär siffror och bokstäver via mobilen m.h.a. Alfamem till
Android.
https://play.google.com/store/search?q=alfamem


On 21 March 2016 at 00:07, Saar Drimer <saar@...3359...> wrote:

Hello everyone,

I work with Inkscape nearly every day, but am now experiencing some
painfully slow performance with some files (that I cannot share
right
now,
sorry!) I'm working with Inkscape 0.91 r13725 on Ubuntu 15.10 with
an
i7-5500 and 16GB of RAM.

The designs are not particularly complex, but have one feature that
might be relevant: I'm working with dimension accurate objects that
can be very small, 0.1mm and below (I design printed circuit
boards).
The slowness becomes painful when zoomed in onto the small objects;
it
happens when I try zooming, choosing objects, moving them, and even
changing tools from 'node' to 'select'. nearly every such operation
I
get the greyed-out Ubuntu stall. Working on the design when zoomed
out
is not practical, but it is quite a bit faster performing.

Another thing that's happening that could be related is the
following
prompts keep appearing on the console:

(inkscape:15569): Pango-CRITICAL **: pango_font_family_list_faces:
assertion 'PANGO_IS_FONT_FAMILY (family)' failed

(inkscape:15569): Gtk-CRITICAL **: IA__gtk_tree_view_scroll_to_cell:
assertion 'tree_view->priv->tree != NULL' failed

I could not find any report for how to handle these, and discover if
they are related to the performance problems.

Searching for a solution through looking at bug reports, I've tried:

* Running with fresh preferences.xml
* Geometric bounding box
* Reducing the complexity of the design
* Hiding layers (there are 24 layers) to only ones that are relevant
for the operation (usually only two layers)
* Hiding rulers and scroll-bars
* Maximising memory and threads (with restart)

I'm out of ideas, and I hope that someone might be able to recommend
something. If there are no ideas, I'll work on a design that I can
share so that we could work though it.

Thanks,
Saar.




------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

------------------------------------------------------------------------------

_______________________________________________
Inkscape-devel mailing list
Inkscape-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-devel

-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2016.0.7538 / Virus Database: 4545/11962 - Release Date: 04/05/16