Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
Is it better to create one Mongo databases per each user with thousand documents in one collection or one database with millions of documents in one collection?
I do not want to exchange data through the users. It will be completely separate.
The most powerful structure to store the information depend by query that you want to perform.
For example, if you want to execute a query between more users should consider the hypothesis of a single private collection.
Mongo db also offers an efficient system for the distribution of the workload across multiple machines in a completely transparent see here
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I need to test the performance of MongoDB and Postgresql in large amount of data, over 5GB, for a college's assignment.
How can I create data for both databases?
Thanks
EDIT:
I found this webpage http://www.generatedata.com where you can download a script to generate the data
First, take a look to How to Generate Test Data on MongoDB. For MongoDB mongoperf i a tool to measure performance of such database on disk. also, you can see MongoDB Benchmarks. For Postgressql you can use pgbench.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I am considering using mongo db (it could be postgresql or any other ) as a data warehouse, my concern is that up to twenty or more users could be running queries at a time and this could have serious implications in terms of performance.
My question is what is the best approach to handle this in a cloud based and non cloud based environment? Do cloud based db's automatically handle this? If so would the data be consistent through all instances if a refresh on the data was made? In a non cloud based environment would the best approach be to load balance all instances? Again how would you ensure data integrity for all instances?
thanks in advance
I think auto sharding is what I am looking for
http://docs.mongodb.org/v2.6/MongoDB-sharding-guide.pdf
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
At the present stage I am searching some alternatives for my futuristic image retrieval project. Some of my friends suggest to use MongoDB for searching and indexing backend. I am a bit biased for this. I don't know whether MondoDB might give fast enough speed for retrieval of about ~10 million images. What is your suggestion for these arguments?
My basic retrieval operation is cosine distance with LHS on image features. Please consider the question in these terms.
You shoud keep in mind that if you are gonna use mongodb for Imgae File Storage, your images file size couldn't be more than 16MB unless you use gridfs
http://java.dzone.com/articles/when-use-gridfs-mongodb
You can gain great performance via mongodb. In my opinion if you want use your system just for Adding data and performing query (but not deleting and modifying them) Mongo is great
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
What are nosql databases?
Nosql database is a buzzword now a days, I searched there are lots of nosql database like: mongodb, hadoop, cassandra...
But still I dont understand how they are different from Relational databases.
nosql databases are key,value storage that provides functionalities/features like replication,fault tolerance,eventual consistency.Relational database is transactional consistent and with primary,secondary indexes,well designed cost/rule based optimizers.
However,nosql scales horizontally and it is hard to scale relational database.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
We are considering Heroku Postgres Crane plan. Anyone knows how many databases can be created in one such plan? Could not get this info anywhere.
Each plan provides only one db. You can have multiple postgres addons to get multiple dbs, but you will be billed per plan/addon. I would recommend using multiple tables instead of multiple dbs for your app.
If you wish to use multiple plans, you can have an unlimited number of dbs per account, but currently, only about ~30 dbs per app before Heroku runs out of identifiers.