On Monday 16 May 2016 12:52:57 Sean Harmer wrote:
> We have a WIP to replace the use of QVariant on the backend of Qt 3D but
> it would benefit all of Qt (including Qt 3D frontend to backend change
> notifications) if we can also improve the locking behaviour of QVariant.
> We have some ideas here
On Montag, 16. Mai 2016 18:06:27 CEST Sean Harmer wrote:
> Probably the biggest hit we see from the use of QVariant in Qt 3D these days
> is the memory allocations for passing around QMatrix4x4's in them. We will
> soon replace these with a strongly typed alternative.
Can you try this patch to see
On segunda-feira, 16 de maio de 2016 18:06:27 PDT Sean Harmer wrote:
> > Uncontended locks in Qt are extremely cheap.
>
> They're better now than they were since Olivier rewrote QReadWriteLock
> recently.
I have a mind to see if a solution inspired by the WTF::Lock solution (see
https://webkit.o
On Monday 16 May 2016 08:22:26 Thiago Macieira wrote:
> On segunda-feira, 16 de maio de 2016 11:52:57 PDT Sean Harmer wrote:
> > We have a WIP to replace the use of QVariant on the backend of Qt 3D but
> > it
> > would benefit all of Qt (including Qt 3D frontend to backend change
> > notifications)
On segunda-feira, 16 de maio de 2016 11:52:57 PDT Sean Harmer wrote:
> We have a WIP to replace the use of QVariant on the backend of Qt 3D but it
> would benefit all of Qt (including Qt 3D frontend to backend change
> notifications) if we can also improve the locking behaviour of QVariant. We
> h
On Monday 16 May 2016 12:32:41 Mark Gaiser wrote:
> Hi,
>
> Just a fyi since the article might be of interest to some on this list.
> I just stumbled upon this github project [1].
> The article and rationale for that project can be found here [2].
>
> It claims to be a stack based "variant" imple
On Montag, 16. Mai 2016 12:32:41 CEST Mark Gaiser wrote:
> Hi,
>
> Just a fyi since the article might be of interest to some on this list.
> I just stumbled upon this github project [1].
> The article and rationale for that project can be found here [2].
>
> It claims to be a stack based "variant
Hi,
Just a fyi since the article might be of interest to some on this list.
I just stumbled upon this github project [1].
The article and rationale for that project can be found here [2].
It claims to be a stack based "variant" implementation made for performance
and as little overhead as possibl
