Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I need to build application with big data (archive) .
I try mongo and mysql but both need much memory .
ex. Mongo need 10G ram for 30G database .
I need a database use less memory , have index , write can slow ,acceptable read .
Why do you need the index? If you can forego the index you might want to look at the MySQL ARCHIVE Storage Engine.
Alternatively, since speed is not a factor, might you be able to compress a portion of the data? If the data is uncompressable, can you store it on a filesystem with links to the data from an indexed database? What are your hardware and OS constraints?