Storing and displaying "large" amount of data

[FreddyKay]

Since you basically have a tabular structure, e.g. several values belonging to one record, each record having the same data fields, maybe consider using a table model and a table view?

Cheers,
_

That might be possible, though I would rather like to have it in textform, as its way easier to use in my opinion. Is it normal, that QTextDocument is causing that much memory usage? If I put all those strings into a QStringList the amount of data in RAM is aprox. 75MB (just like a TextFile if I save all entries into a file). The TextDocument needs almost 15 times as much apparently. This makes me believe I made a mistake somewhere and there are maybe memory leaks or data dulpicates or somehting.

Can you think of a way that would reduce memory usage and display time to more reasonable levels, where I can still use the QTextEdit / QPlainTextEdit?

[d_stranz]

I don't see any obvious memory leaks, unless you are calling this method more than once. Each time through you create a new QTextDocument instance; if you aren't getting rid of these and are calling this method over and over, then you'll keep accumulating dangling pointers to the old documents and using up more and more memory.

This really does scream to be represented as a table. You're formatting it that way, so just use a QTableWidget or QTableView and turn off the grid lines.

The amount of time could be because the document is recomputing its internal layout with each line you add to it and possibly pushing everything onto undo / redo stacks with each addition. The default value for the undoRedoEnabled property is true, and I don't see where you disable it. So you might have an undo stack with 500K blocks on it.

[FreddyKay]

I don't see any obvious memory leaks, unless you are calling this method more than once. Each time through you create a new QTextDocument instance; if you aren't getting rid of these and are calling this method over and over, then you'll keep accumulating dangling pointers to the old documents and using up more and more memory.

This really does scream to be represented as a table. You're formatting it that way, so just use a QTableWidget or QTableView and turn off the grid lines.

The amount of time could be because the document is recomputing its internal layout with each line you add to it and possibly pushing everything onto undo / redo stacks with each addition. The default value for the undoRedoEnabled property is true, and I don't see where you disable it. So you might have an undo stack with 500K blocks on it.

Alright. Thanks a lot you two. I'll give QTableView a try, though I will also try disabling the undoRedo thingy.