mysql design: which is better, many columns or many rows?
===

i need to design a new table for my project, which basically holds a list of 41 numbers per key.
the first number in the list is some distance measurements,
while the rest of the numbers represent weighted bins of percentages as such:

the first ten percentiles are 1% each

the next ten are of 2% each

the next ten are of 3% each

and the next ten are of 4% each

which all some up to 1*10 + 2*10 + 3*10 + 4*10 = 100%

the normal usage of this data would be summing the bins *vertically*. 
(i.e. key1-bin1 + key2-bin1 + .. ; key1-bin2 + key2-bin2 + .. ; etc. )


now, assuming this will never change and there will always be 40 bins with the same bin dispersion, which is better?:

- one line per key of the form - key, distance, bin1, bin2... bin40

or

- 41 lines per key of the form - key, bin_number, value where bin_number -1 holds the distance

the obvious advantage of the first option is the reduction of data duplication, plus i really don't like my "-1" workaround..

but this feels really dirty and extremely "hard-coded", and i remember being taught that databases somehow "prefer" the second option and are designed to handle it better than the first in terms of compression, indexing etc.
(plus the queries will probably look nicer in the second option, but i can live with ugly queries in my code)

thanks!