Gentoo Archives: gentoo-user

From: Daniel Troeder <daniel@×××××××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] how to use my SSD the right way ;-)
Date: Sat, 04 Jan 2014 17:51:37
Message-Id: 52C84A18.8000703@admin-box.com
In Reply to: Re: [gentoo-user] how to use my SSD the right way ;-) by Alan McKinnon
1 Am 03.01.2014 15:07, schrieb Alan McKinnon:
2 > On 03/01/2014 15:13, William Kenworthy wrote:
3 >> On 03/01/14 15:34, Alan McKinnon wrote:
4 >>> On 03/01/2014 09:25, Stefan G. Weichinger wrote:
5 >>>> Am 03.01.2014 07:52, schrieb Alan McKinnon:
6 >>>>> On 03/01/2014 00:46, Stefan G. Weichinger wrote:
7 >>>>>> BFQ only for the SSDs ?
8 >>>>>
9 >>>>> Yes. The scheduler knows how to deal with SSDs while keeping everything
10 >>>>> responsive even under load.
11 >>>>>
12 >>>>> BFQ seems a good fit for your workcase - desktop/laptop. For those,
13 >>>>> interactive performance is the most important thing.
14 >>>>
15 >>>> So you set BFQ for the SSDs and CFQ for the hdds ? I have both in my
16 >>>> desktop.
17 >>>>
18 >>>>
19 >>>>
20 >>>>
21 >>>
22 >>> BFQ for both is the recommendation.
23 >>>
24 >>> But do try it both ways to see how it performs and compare.
25 >>>
26 >>
27 >> hmm, is BFQ good for VM's too? I am currently using noops (storage is
28 >> ceph) and was going to experiment but have not had the time yet.
29 >
30 >
31 > I have no idea, but I'd like to find out.
32 >
33 > Instinct tells me one of the host or guest should be NOOP so that the
34 > other one can get on with scheduling without conflict. But I also reckon
35 > the question is waaaay more complex than that.
36 A VM should always use noop, as it doesn't know about the physical
37 layout of the disk (except if you did pass the devices card through...
38 with a SAS interface over PCIe for example). What IO-scheduler you'd use
39 for the host depends on your hardware and the desired optimization goal
40 (throughput vs latency).
41
42 My _personal_ opinion for the desktop(!): If you're content with the
43 general performance I would not optimize for your most common use case
44 (global maximum), but for the use case that is not-to-uncommon and that
45 benefits most of it. The idea is, that if most of you life is good, try
46 to make the remaining part suck less :)
47
48 Greetings,
49 Daniel

Attachments

File name MIME type
signature.asc application/pgp-signature