Re: [Interest] Qtcontainerbench std::vector vs QVector

2015-07-28 Thread Allan Sandfeld Jensen
On Monday 27 July 2015, Gunnar Roth wrote: > Hi Constantin. > Thank you for looking at my benchmark. > > > Am 24.07.2015 um 08:57 schrieb Constantin Makshin : > > > > Well, after looking at the code I can say that the was you wrote this > > benchmark "abuses" the QVector's copy-on-write semantic,

Re: [Interest] Qtcontainerbench std::vector vs QVector

2015-07-28 Thread André Somers
Op 27-7-2015 om 21:42 schreef Gunnar Roth: > Hi Constantin. > Thank you for looking at my benchmark. > >> Am 24.07.2015 um 08:57 schrieb Constantin Makshin : >> >> Well, after looking at the code I can say that the was you wrote this >> benchmark "abuses" the QVector's copy-on-write semantic, makin

Re: [Interest] Qtcontainerbench std::vector vs QVector

2015-07-27 Thread Constantin Makshin
On 07/27/2015 10:42 PM, Gunnar Roth wrote: > Hi Constantin. > Thank you for looking at my benchmark. > >> Am 24.07.2015 um 08:57 schrieb Constantin Makshin : >> >> Well, after looking at the code I can say that the was you wrote this >> benchmark "abuses" the QVector's copy-on-write semantic, maki

Re: [Interest] Qtcontainerbench std::vector vs QVector

2015-07-27 Thread Thiago Macieira
On Monday 27 July 2015 21:42:58 Gunnar Roth wrote: > But the results show still a 50% better performance for std::vector when > inserting and 2 times better performance when iteration non const. In the > other cases QVector is on par with std::vector. So i still say choose > QVector only when you r

Re: [Interest] Qtcontainerbench std::vector vs QVector

2015-07-27 Thread Gunnar Roth
Hi Constantin. Thank you for looking at my benchmark. > Am 24.07.2015 um 08:57 schrieb Constantin Makshin : > > Well, after looking at the code I can say that the was you wrote this > benchmark "abuses" the QVector's copy-on-write semantic, making it > somewhat biased towards std::vector — you us

Re: [Interest] Qtcontainerbench std::vector vs QVector

2015-07-23 Thread Constantin Makshin
Well, after looking at the code I can say that the was you wrote this benchmark "abuses" the QVector's copy-on-write semantic, making it somewhat biased towards std::vector — you use only non-const versions of QVector::begin(), QVector::end() and indexing methods. That leads to a lot of [obviously

Re: [Interest] Qtcontainerbench std::vector vs QVector

2015-07-22 Thread Gunnar Roth
> Am 23.07.2015 um 07:00 schrieb Constantin Makshin : > > "vector" branch is identical to "master“. Not anymore ;-) Thanks for the information. ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest

Re: [Interest] Qtcontainerbench std::vector vs QVector

2015-07-22 Thread Constantin Makshin
"vector" branch is identical to "master". On 07/22/2015 10:20 PM, Gunnar Roth wrote: > Hi, > for whom it may concern i post my results for vector iterating using > iterator and index plus insert via push_back. > > the test code is at https://github.com/gunrot/qtcontainerbench in > branch vector.

[Interest] Qtcontainerbench std::vector vs QVector

2015-07-22 Thread Gunnar Roth
Hi, for whom it may concern i post my results for vector iterating using iterator and index plus insert via push_back. the test code is at https://github.com/gunrot/qtcontainerbench in branch vector. it runs over N containers where N=min(1,10/co