Mail Archives: geda-user/2018/05/08/05:04:40
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-545642738-1525770170=:8169
Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE
Hello Michael,
On Tue, 8 May 2018, michalwd1979 (michalwd1979 AT o2 DOT pl) [via geda-user AT delori=
e.com] wrote:
>
>Here it is from 21.5 to 22.7 with 22.1 average. Very similar to single lay=
er
>version.=C2=A0
Great, thanks! This means it is not the layer compositing that's slow.
<snip>
>One more notice: With my board loaded even moving a cursor causes instant
>100% cpu load for a few seconds, with benchmark() it is the same. Mainline
>or opengl pcb never causes high cpu usage even with furious panning or
>rotating. While sometimes the movement is not super smooth, GUI is always
>very responsive. This is not the case with pcb-rnd, here I have to wait fo=
r
>a menu to open after for example cursor movement. Also turning ON/OFF
>"subcircuits" layer makes a huge difference - maybe we are looking in the
>wrong place??
Thanks, that's the next we can look at.
I don't think we are looking in the wrong place. Knowing how the rendering=
=20
works, I have a list of tests to perform to see what's slow and what's not=
=20
slow. It may be that we figure at the end that it was only a single thing=
=20
that caused all slowness, or it may be that a combination of 4..5 things=20
took the time. We'll find only if we test them each.
The subc bbox is a xor draw thing; so what's next on my list (see also the=
=20
1024 resistors test) is checking if the number of xor drawn lines matter.
Mouse cursor movement makes the crosshair move. The crosshair is xor-drawn=
=20
too. If our gl xor draw mechanism is slow in general, that explains why=20
any pan or cursor move is slow.
Another rather unfortunate thing that happens when you move the crosshair=
=20
is a full screen redraw, because of the invalidations. It's how we=20
inherited the code from the 2011 version - it's on my list to fix, but=20
haven't got to fix it yet. Tomorrow morning I will prepare something for=20
turning off the crosshair so we can test that too.
Then I also plan to have an object type based test.
So a lot of tests to do before we get a clear picture.
Regards,
Igor2
--0-545642738-1525770170=:8169--
- Raw text -