What is the design idea of user portrait database?

We want to create a database of user image analysis, the main information content and is the user's personal information and purchase order information, order turnover these.

Now want to export these data, re-storage, do a portrait analysis, but hundreds of thousands of of the amount of data in a table, the response is too slow, but according to the product type separate multiple data table storage, correlation query to splicing a lot of fields.

I just get started, the idea is too simple, trouble master to point out the storage ideas of the database

Reply content:

We want to create a database of user image analysis, the main information content and is the user's personal information and purchase order information, order turnover these.

Now want to export these data, re-storage, do a portrait analysis, but hundreds of thousands of of the amount of data in a table, the response is too slow, but according to the product type separate multiple data table storage, correlation query to splicing a lot of fields.

I just get started, the idea is too simple, trouble master to point out the storage ideas of the database

The stored field definition should be about the same as the volume, the index definition of the table, the data segment to get it, and then the analysis, which is what most companies are doing

Hundreds of thousands of of the data volume is large? Query 1ms is not available

