great video. my notes: - for the sharding distribution, you can use a hash function on a shard key, or a range of values for your shard key. Each sharding node gets 1 chunk (and vise versa); a chunk is a set of documents with contiguous shard key values (in case of _range_ sharding). If you often use range based queries (eg $lt, $gt on your shard key), then you'll benefit from using a _range_ sharding ; otherwise hash sharding is almost always the best choice. - indexes add to the _write_ workload on your DB, as their value have to be added to indexes. ¿Is this done synchronously? - 24:30 A "working set" is the data that your application is constantly requesting. But that includes both the actual documents AND all their related indexes. But the full working set has to fit in memory for your request to perform efficiently ; so by adding unecessary indexes, you are increasing the risk of making your working set too big for the memory of your sharding node.
Thanks for the interesting content! 😍 I’ve got a question: 🤨 I have these words 🤨. (behave today finger ski upon boy assault summer exhaust beauty stereo over). I’d be grateful for some help. 🙌
Hey Prakash and Dai, Thanks for the insights, actually I'm new to mongodb and having a lot of questions, I hope you guys will help me, How frequent balancer runs? do we have any setting for balancer to run for every 1 minute or 10 minute etc? if we have where and how can we do that?
great video.
my notes:
- for the sharding distribution, you can use a hash function on a shard key, or a range of values for your shard key. Each sharding node gets 1 chunk (and vise versa); a chunk is a set of documents with contiguous shard key values (in case of _range_ sharding). If you often use range based queries (eg $lt, $gt on your shard key), then you'll benefit from using a _range_ sharding ; otherwise hash sharding is almost always the best choice.
- indexes add to the _write_ workload on your DB, as their value have to be added to indexes. ¿Is this done synchronously?
- 24:30 A "working set" is the data that your application is constantly requesting. But that includes both the actual documents AND all their related indexes. But the full working set has to fit in memory for your request to perform efficiently ; so by adding unecessary indexes, you are increasing the risk of making your working set too big for the memory of your sharding node.
Thanks for the interesting content! 😍 I’ve got a question: 🤨 I have these words 🤨. (behave today finger ski upon boy assault summer exhaust beauty stereo over). I’d be grateful for some help. 🙌
Hey Prakash and Dai, Thanks for the insights, actually I'm new to mongodb and having a lot of questions, I hope you guys will help me, How frequent balancer runs? do we have any setting for balancer to run for every 1 minute or 10 minute etc? if we have where and how can we do that?
Thanks.