What database architecture to choose for an application with a large number of accounts?

Question

MySQL

Good evening!
There is a web application, it has a database in which there is a table of registered accounts. Each account has its own set of data - users, tasks, goods, payments, etc., about 15 tables.
The question is about the architecture - in this case, would it be correct to store the data associated with the accounts in the same tables, or would it be better for each account to create a separate set of tables within the same database?
In other words, what is better - to have 15 tables in one database - tasks, goods, payments, etc. with 100,000 records each, or have 1500 tables with 1000 records each?
As an example of table naming:
_<table name>
1_users
1_payments
1_products
2_users
2_payments
2_products etc.

Answer 1

100000 are trifles, it is not necessary to produce tables for each user.