[DOCS-3815] Production notes: use noop scheduler for virtualized disks Created: 24/Jul/14 Updated: 16/Mar/15 Resolved: 25/Aug/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.10 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Alexander Komyagin | Assignee: | Tim Slavin |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 9 years, 25 weeks, 2 days ago |
| Description |
|
If your mongo servers are virtualized, and disks are attached through the hypervisor (i.e. not directly to the VM), you can get better performance with the "noop" scheduler, because hypervisor will have it own scheduler to take care of disk writes. |
| Comments |
| Comment by Githook User [ 25/Aug/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |
| Comment by Githook User [ 25/Aug/14 ] |
|
Author: {u'username': u'TimSlavinMongoDB', u'name': u'Tim Slavin (MongoDB)', u'email': u'tim.slavin@10gen.com'}Message: Signed-off-by: Sam Kleinman <samk@10gen.com> |