Does an object occupy a lot of memory?

Question

If in a database each record is an object, in 25,000 records, managing resources can be an issue.
What solutions do I have to manage resources in an object-oriented database?

Answer 1

Objects need differently much memory depending on how many and what sort of data members they have.

So wouldn't it largely just depend on how well and efficiently the object-oriented system is designed?

I mean, if you need to store the data, it will have to sit somewhere, OOP or not...

Answer 2

One is to not store empty records.

Answer 3

Data compression maybe another strategy.

Answer 4

What c ++ resources would you use for a good optimization?:
Design criteria? memory management? threads?
An object-oriented database should be limited to a small number of records?

Answer 5

Taking advantage of the Windows error and the advantage of Linux, how to design it so that everything is not available all the time ?. How to create the queries without falling into duplication of data? .. It seems that it will be worth stopping the time it takes in thorough design.
I thought about segmenting the data and grouping them with some criteria, before compressing them ... so that when manipulating them, I don't have to decompress everything at once ...
As I would be directed to a medical clinic, I could group it by diagnoses or service departments: Traumatology, Urology, laboratory, etc.