I am currently storing data in fields as shown below. Each of these pricing fields has two database rows associated with it, and there is up to 24 of these tables for a house. This therefore means that in the worst case, a house has 1,440 rows of prices associated with it.
Is this going to lead to a much slower load time for a page, if all this data needs to be loaded to create a page? When doing an availability search for a long time in the future (so worst case), this data needs to be potentially loaded for all houses so that is up to 80,000 rows that need to be loaded.
I did think that it might be better practice to store this in a serialized format, where 1,440 would be reduced to 48 rows per house. Is this a good idea?