Does the number of MySQL table columns affect performance?

Question

MySQL

I have 100 columns with data in my MySQL table of goods, and this is already a shortened version, since somewhere around 50 were separated into tables with additional characteristics of goods. How much will this affect the read / write time in the future, when 1,000,000 positions will be allowed? 100,000,000 items? Should I distribute the rest of the data to additional tables or make no difference and leave it like that?

Answer 1

I have 100 columns with data in my MySQL product table

I would still do this using product types that will be stored in a separate table, but here - only ID-shniks for type structures. Also, all extras. characteristics - are connected through the ID-shniks of the fields-characteristics, which are also stored in other tables.
As a result: it will be convenient to create a faceted filter (to search for products with a certain set) and do the maximum indexing through ID fields inside the database.

Answer 2

No, clusters are not required.
It is worth paying attention to columnar DBMS , which solve the problem of optimal storage and access to data with a large number of columns.
MonetDB, Druid or e.g. MariaDB ColumnStore development product (full SQL supported) as a continuation of InfiniDB development.
There is one article that talks about ways to store data in tables in traditional DBMS:
Table structure for an online store product catalog

EAV stands for Entity-attribute-value or in Russian: object-attribute-value. It is a data model for describing entities in which the number of attributes (properties, parameters) can be potentially large.