Memory difference between QMap<MyInst,QColor> and QMap<MyInst,QString)

kshegunov

@Qt-Enthusiast
No! 1 character in QString is 2 bytes (it uses unicode), so the 6 characters you need to store the color will be 12 bytes vs the 3 (or 4 bytes with alpha) you need for representing a color. But again, why do you care? Just use what makes sense - QColor for colors, QString for strings ...

@mrjj
sizeof isn't useful here:

sizeof(QString) == sizeof(void *)

mrjj

@kshegunov
yes u are right ( as always)
Just meant for checking how much QColor will take.

kshegunov

@mrjj
It's easier to just check it up:
http://code.qt.io/cgit/qt/qtbase.git/tree/src/gui/painting/qcolor.h#n227

1 enum which is the word's size + 5 shorts in the union.
For a 64 bit machine this is ~~6 shorts~~ 5 shorts and an int64 or ~~12 bytes~~ 18 bytes. So there's no difference.

EDIT:
My math skills apparently suck.
A QString represented color will require 12 bytes for the 6 characters + 8 bytes on a 64 bit OS for the pointer + 4 bytes for the atomic reference counter used in the implicit sharing, which totals to 24 bytes

mrjj

@kshegunov
also, unless he has a 10.000.000
it might not really matter :)

SGaist

Hi,

And to add my fellows, if you have a doubt: benchmark. That way you'll what suites your needs best.

Qt Enthusiast

Sorry does that mean QString takes more memory that QColor

Qt Enthusiast

EDIT:
My math skills apparently suck.
A QString represented color will require 12 bytes for the 6 characters + 8 bytes on a 64 bit OS for the pointer + 4 bytes for the atomic reference counter used in the implicit sharing, which totals to 24 bytes

This is not clear to me how much memory QString takes

mrjj

hi
24 bytes it seems. :)

Qt Enthusiast

so QString takes more memory that QColor ?

mrjj

@Qt-Enthusiast
yes. on 64 bit, even more.

kshegunov

@Qt-Enthusiast
18 bytes for a QColor instance vs about 30 bytes for a QString object with 6 letters (QString will also keep one zero character at the end and will store the length, as addition to the things I've described in my edit). So yes, QColor will take less memory.

But I just can't stress this enough: use what makes sense. Even if QString were more memory efficient, the complications and the needed CPU time for conversions between colors and strings just makes it unsuitable. And small wonder, it's supposed to be a general purpose string, not a color. There's a separate class that represents colors, so you should use that in any case and not worry about how much bytes anything takes unless you hit the memory limit (which seems doubtful at this point).

jsulm

@kshegunov Yes, using QString instead of QColor to represent a colour just to save some bytes is an example for how not to optimize software.
@qtEnthusiast why not use an 32bit unsigned int to represent a colour? This way you only need 4 bytes.

mrjj

@jsulm
Following your thought of unsigned int

Would
QMap<MyInst,QRgb);

be as good?

It does seems
QColor::QColor(QRgb color)

will ignore alpha.

jsulm

@mrjj It depends on the requirements: is alpha needed?

mrjj

@jsulm
Hi
Not 100% sure but my guess would be
yes from what he posted so far.

update:
funny enough it seems to like alpha the other way
QRgb QColor::rgba() const

Qt Enthusiast

Can u tell me how to represent integer for colors because we can have millions of colors ?

jsulm

@Qt-Enthusiast 32bit integer can represent billions of values/colors.
RGB - means 1byte for red, 1byte for green and one byte for blue. Since 32bit integer consists of 4 bytes you still have one byte for alpha channel.

jsulm

@Qt-Enthusiast See here: http://doc.qt.io/qt-5.7/qcolor.html#QRgb-typedef

SGaist

What exactly do you want to do with that map ?