How hard is it to work with a large MySQL database?

I have such a need to have a user base, and that fields (id, nick, name, surname, email, phone, city, age, photo and even field 4 -> in total about 15)

1) How much space will occupy the base with 1 million such records?
2) How difficult are the queries to sample from such a large base? If the base will increase to 10 million, and the duration/severity of the queries is proportional to 10 times increase?
3) what options should pay attention when choosing hosting/vps/vds under such a basis?
July 9th 19 at 11:12
3 answers
July 9th 19 at 11:14
Solution
1. approximately 700 megabytes
2. depends on the indexes of the organization. If properly placed indexes you will have no problems and queries will be processed quickly. I have one site with 60mln records in one table - all the rules.
3. It is advisable to take with ssd, but these are more expensive.
Well, to have a database of 60 million records, do simple queries like Select all records where field1=value1 when the website traffic of 50 million... after all, there is no need to buy any expensive servers, and a VPS will be sufficient for 50 bucks? - christina commented on July 9th 19 at 11:17
: 50 thousand unique visitors a day - if we assume that they come only during the day - that will be released in about 1 request per second, so Yes, this will be enough - Chyna.Jerde commented on July 9th 19 at 11:20
: thanks! so I will not be afraid of the volume) good luck! - christina commented on July 9th 19 at 11:23
VDS hosting is now even an inexpensive type ruweb.net where I have to spin system with 5000 requests per second rate for the slightly cheaper 200 rubles are on the SSD. - Weston98 commented on July 9th 19 at 11:26
should not be afraid of the volume, and the number of requests per unit time. - Weston98 commented on July 9th 19 at 11:29
July 9th 19 at 11:16
1) How much space will occupy the base with 1 million such records?
In current situation minor. The rough upper limit is 10Gb (plus or minus a couple petabytes).

How difficult are the queries to sample from such a large base?
Depends on the queries.

If the base will increase to 10 million, and the duration/severity of the queries is proportional to 10 times increase?
A direct correlation between table size and query performance no moving parts in this process quite a lot - it is and index and the structure of the queries.

What options should pay attention when choosing hosting/vps/vds under such a basis?
For spherical base in a vacuum, will work with the spherical application in vacuum take the spherical VDS in vacuum, for which you have enough money. If it does not deal with spherical load in the vacuum, take VDS powerful. Live - Die - Repeat.

PS
How hard is it to work with a large MySQL database?
The evening begins paws ache and the tail falls off, but overall tolerable.
July 9th 19 at 11:18
1 million records to a modern DBMS and modern server - load anything.
I have billions of records spinning and does not slow down.
If slow, the fact that you are not so designed.

Google - the correct indexing of the database.
And for very large loads (not the volume, not the amount of data and number of requests, number of users) - sharding.

Even here poleznyak:
https://habrahabr.ru/post/113298/
About Tarantool can not read. You don't need.
But in the beginning - about the proper use of MySQL.

UPD:
The right choice VPS????
Me 200 rubles VPS with a small margin of 5,000 requests per second processed.
All the matter in the proper design/implementation of the production - database, indexes, queries, processing requests.

UPD:
1) How much space will occupy the base with 1 million such records?


Take the size of each entry (summerwash the average length of a surname, a name, a city name, etc.) multiplied by a million and multiply it by 3.

Why do you want the database to store the photo? This is not a typical task for a database.
Maybe you meant to link?

2) How difficult are the queries to sample from such a large base? If the base will increase to 10 million, and the duration/severity of the queries is proportional to 10 times increase?


Nobody needs all your millions. As a rule.

Queries will run for a reasonable time only to a small part of the database.

So productive did not fall, to avoid Full Scan the correct indexes. Correct. Make them based on what your conditions in the where clause.

The above is about the search.

But data transfer - Yes.
If you need to transfer 100 records or 100,000 records, then obviously that will take longer. But this is not a problem of the database. You have to make the maximum amount of information in a single request to. But everything else - not the task of the database.

3) what options should pay attention when choosing hosting/vps/vds under such a basis?


VDS modern, as a rule, easily scales upwards. Take the cheapest. If it's not enough to increase the rate. Reboot. Receive more resources.

Find more questions by tags MySQL