QCString construction

[David Faure]

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, faure at kde.org, dfaure at klaralvdalens-datakonsult.se
KDE/KOffice developer, Qt consultancy projects
Klarälvdalens Datakonsult AB, Platform-independent software solutions
-------------- next part --------------
A non-text attachment was scrubbed...
Name: qcstring_perf.cpp
Type: text/x-c++src
Size: 1280 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/kde-optimize/attachments/20070210/46eb96de/attachment.bin