Re: QCString construction

On Saturday 10 February 2007, David Faure wrote:
> Here's a benchmark I wrote which proves how much we can
gain (and it also proves
> that the resulting qcstring is correct ;)
> 
> Results on amd64 with -g3 and no optimization:
> QCString(char*) took 1582 milliseconds
> QCString(n)+memcpy took 134 milliseconds
> QCString()+setRawData took 31 milliseconds
> 
> Results on i686 with -O2:
> QCString(char*) took 2558 milliseconds
> QCString(n)+memcpy took 161 milliseconds
> QCString()+setRawData took 35 milliseconds

I forgot to attach the benchmark - in case someone spots an
error, or an even better way to do it.

-- 
David Faure, faurekde.org, dfaureklaralvdalens-datakonsult.se
KDE/KOffice developer, Qt consultancy projects
Klarälvdalens Datakonsult AB, Platform-independent software
solutions

_______________________________________________
Kde-optimize mailing list
Kde-optimizekde.org
ht
tps://mail.kde.org/mailman/listinfo/kde-optimize