The younger brother is trying to write an application similar to the monitoring center. the amount of data is not much. data records per day. the database size increases by 20 mb per day. data must be analyzed from various dimensions. in terms of time, data center, and machine model. if I retrieve pieces of data at a time, it will take 2 s for mysql to query by default.
The younger brother is trying to write an application similar to the monitoring center. the amount of data is not much. 12 million data records per day. the database size increases by 20 mb per day. data must be analyzed from various dimensions. in terms of time, data center, and machine model. if I retrieve 12 million data records at a time, it will take 2 s for mysql to query by default.
The younger brother is trying to write an application similar to the monitoring center. There is not much data, but a lot less. There are 12 million pieces of data every day. The database size increases by 20 mb every day.
When data is available, it is necessary to analyze data from various dimensions, including time, data center, and machine model. If I retrieve 12 million pieces of data at a time, it is not said that mysql takes time to query data under the default configuration.2 sThe above, and it takes nearly to create such a large array in ruby.10 sNot to mention making more judgments and statistical logic in the future. I can't imagine what would happen if I had to analyze data for a week or a month.
So I came up with"Should I try mongodb"This time, I am on the road to reading mongodb documents. By the way, I would like to ask my predecessors if mongodb can satisfy my ideas quickly (referring to performance). Thank you.
Original article address: Should I use mongodb? (Can mongodb better solve my problems than mysql ?), Thanks to the original author.