Recently, I encountered a big problem in my project.When my app running, I got approximately \[code\]20 data-nodes per second\[/code\]. If I write \[code\]one data-node into a mysql record\[/code\], mysql will \[code\]expand to 720,000 records in one hour\[/code\] when there are 10 people using my app simultaneously. Obviously, the way of storage is not a good choice. What I intend to achieve regarding performance is to \[code\]select records from database\[/code\] according to specific conditions, then \[code\]show them using chart\[/code\]. All this will be done in server-side, which is structured in Spring, SpringMVC, Mybatis, etc. Could anyone offer me some suggestions on how to store those large amount of data in database? Thanks a lot!P.S.: \[code\]Data Structure\[/code\] for my data-node:
Can MySQL bear large amounts of records?
- Thread starter Nicole
- Start date