You are absolutely right. But that comparison was very interesting for
SObjectizer’s users...
From: Romain Beaumont
Sent: Thursday, June 12, 2014 3:11 PM
To: Igor Mironchik
Cc: Rainer Wiesenfarth ; interest@qt-project.org
Subject: Re: [Interest] How to speed-up chameleons
"SObjectizer
er and nail, lol :)
>
> -Original Message-
> From: Rainer Wiesenfarth
> Sent: Thursday, June 12, 2014 1:06 PM
> To: interest@qt-project.org
> Subject: Re: [Interest] How to speed-up chameleons
>
> > Ah, ok. I understand. You suggest to not use signals/slots and use
> &g
This small task was done to compare Qt's messaging system with SObjectizer's
messaging system :)
P.S. Thanks for hammer and nail, lol :)
-Original Message-
From: Rainer Wiesenfarth
Sent: Thursday, June 12, 2014 1:06 PM
To: interest@qt-project.org
Subject: Re: [Interest] How t
From: igor.mironc...@gmail.com
> Ah, ok. I understand. You suggest to not use signals/slots and use semaphore
> instead.
>
> Well. I think this will improve performance. But it will not use messaging
> system of Qt :)
http://en.wiktionary.org/wiki/if_all_you_have_is_a_hammer,_everything_looks_l
-project.org
Subject: Re: [Interest] How to speed-up chameleons
Hi.
What might be faster? One more synchronization primitive in the code will
increase performance?
From: Romain Beaumont
Sent: Thursday, June 12, 2014 9:48 AM
To: Igor Mironchik
Cc: interest@qt-project.org
Subject: Re: [Interest] How to
Hi.
What might be faster? One more synchronization primitive in the code will
increase performance?
From: Romain Beaumont
Sent: Thursday, June 12, 2014 9:48 AM
To: Igor Mironchik
Cc: interest@qt-project.org
Subject: Re: [Interest] How to speed-up chameleons
It might not be necessary (ie you
gt;
> Most slow place is QEventDispatcherWin32::processEvents()
>
> *From:* Romain Beaumont
> *Sent:* Wednesday, June 11, 2014 7:54 PM
> *To:* Igor Mironchik
> *Cc:* interest@qt-project.org
> *Subject:* Re: [Interest] How to speed-up chameleons
>
> "first chameleon s
: interest@qt-project.org
Subject: Re: [Interest] How to speed-up chameleons
"first chameleon should wait a second;" this sound like semaphore to me, but I
don't know this chameleon problem.
What part of Qt is causing it to be slow ? QThread ? the signal/slot ?
2014-06-11 18:51 GM
rom:* Romain Beaumont
> *Sent:* Wednesday, June 11, 2014 5:12 PM
> *To:* Keith Gardner
> *Cc:* igor.mironc...@gmail.com ; interest@qt-project.org
> *Subject:* Re: [Interest] How to speed-up chameleons
>
> Hi,
> Why do you need to use Qt signals/slots ?
> Isn't there something mo
Hi.
What do you suggest?
From: Romain Beaumont
Sent: Wednesday, June 11, 2014 5:12 PM
To: Keith Gardner
Cc: igor.mironc...@gmail.com ; interest@qt-project.org
Subject: Re: [Interest] How to speed-up chameleons
Hi,
Why do you need to use Qt signals/slots ?
Isn't there something
Hi,
Why do you need to use Qt signals/slots ?
Isn't there something more appropriate to this task ?
2014-06-11 15:36 GMT+02:00 Keith Gardner :
> I have one question to you. Why new syntax of QObject::connect() improve
>> performance for a 5%.
>>
>> I mean that if in code change
>>
>> connect( se
>
> I have one question to you. Why new syntax of QObject::connect() improve
> performance for a 5%.
>
> I mean that if in code change
>
> connect( sender, SIGNAL( signal() ), receiver, SLOT( slot() ) );
>
> to
>
> connect( sender, &Sender::signal, receiver, &Receiver::slot );
>
> then code works f
Hi guys,
I have one question to you. Why new syntax of QObject::connect() improve
performance for a 5%.
I mean that if in code change
connect( sender, SIGNAL( signal() ), receiver, SLOT( slot() ) );
to
connect( sender, &Sender::signal, receiver, &Receiver::slot );
then code works faster... W
13 matches
Mail list logo
