Mail Archives: geda-user/2018/05/17/07:35:17
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
--0-1677840600-1526556901=:8169
Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE
Hello Michael,
On Thu, 17 May 2018, michalwd1979 (michalwd1979 AT o2 DOT pl) [via geda-user AT delor=
ie.com] wrote:
>1. subcircuits "layer" =C2=A0off, but top silk on - this way we measure ho=
w
>much does it cost to render all the refdes text objects on silk
>
>
>Much faster, benchmark says 1.4, however still rather unusable. It is
>possible however to zoom or pan (2-3s for a single step zoom).
>
>
>2. subcircuits "layer" on, but top silk off - this way we render about
>the
>same thing, just by a different part of the code
>
>
>Turning subcircuits ON stops everything for very long time (~30-40s) only
>after that it was possible to do benchmark. Result is 0.1, but as I said i=
t
>seems slower. If the subcircuits are ON, turnig top-silk ON/OFF makes no
>perceptible difference.
Very good, thanks! That's what I suspected: there is some slowness when we=
=20
need to render a lot, but a real unreasonable amount of slowness comes in=
=20
for the subcircuit refdes text. I think it's best to start optimizing the=
=20
slowest parts.
We'll work on these after the release.
<snip>
>By the way, am I the only person that noticed speed/text problems? Is my P=
C
>really so much slower then current machines or was my board so complex :-)=
?
I think it is a combintion of:
- a lot of development going into pcb-rnd all the time, which means many=20
of our production users are a few releases behind
- the subcircuit refdes text display is a relatively new feature
- you probably have larger and more complex board than the average
- you probably have older hardware than the average
So you are the first to report this specific problem. But now that we=20
debugged this much, we understand the cause better and I am positive we=20
can speed it up a bit. Both with optimizations in core drawing routines=20
(that will affect all HIDs) and with gl rendering specific optimizations.
I have old hardware, but I don't use gl, so I can't test that part. I rely=
=20
on users to test it.
Best regards,
Igor2
--0-1677840600-1526556901=:8169--
- Raw text -