Re: [Xen-devel] dm-band: The I/O bandwidth controller: Performance Report
Hi, > you mean that you run 128 processes on each user-device pairs? Namely, > I guess that > > user1: 128 processes on sdb5, > user2: 128 processes on sdb5, > another: 128 processes on sdb5, > user2: 128 processes on sdb6. "User-device pairs" means "band groups", right? What I actually did is the followings: user1: 128 processes on sdb5, user2: 128 processes on sdb5, user3: 128 processes on sdb5, user4: 128 processes on sdb6. > The second preliminary studies might be: > - What if you use a different I/O size on each device (or device-user pair)? > - What if you use a different number of processes on each device (or > device-user pair)? There are other ideas of controlling bandwidth, limiting bytes-per-sec, latency time or something. I think it is possible to implement it if a lot of people really require it. I feel there wouldn't be a single correct answer for this issue. Posting good ideas how it should work and submitting patches for it are also welcome. > And my impression is that it's natural dm-band is in device-mapper, > separated from I/O scheduler. Because bandwidth control and I/O > scheduling are two different things, it may be simpler that they are > implemented in different layers. I would like to know how dm-band works on various configurations on various type of hardware. I'll try running dm-band on with other configurations. Any reports or impressions of dm-band on your machines are also welcome. Thanks, Ryo Tsuruta -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Xen-devel] dm-band: The I/O bandwidth controller: Performance Report
Hi, you mean that you run 128 processes on each user-device pairs? Namely, I guess that user1: 128 processes on sdb5, user2: 128 processes on sdb5, another: 128 processes on sdb5, user2: 128 processes on sdb6. User-device pairs means band groups, right? What I actually did is the followings: user1: 128 processes on sdb5, user2: 128 processes on sdb5, user3: 128 processes on sdb5, user4: 128 processes on sdb6. The second preliminary studies might be: - What if you use a different I/O size on each device (or device-user pair)? - What if you use a different number of processes on each device (or device-user pair)? There are other ideas of controlling bandwidth, limiting bytes-per-sec, latency time or something. I think it is possible to implement it if a lot of people really require it. I feel there wouldn't be a single correct answer for this issue. Posting good ideas how it should work and submitting patches for it are also welcome. And my impression is that it's natural dm-band is in device-mapper, separated from I/O scheduler. Because bandwidth control and I/O scheduling are two different things, it may be simpler that they are implemented in different layers. I would like to know how dm-band works on various configurations on various type of hardware. I'll try running dm-band on with other configurations. Any reports or impressions of dm-band on your machines are also welcome. Thanks, Ryo Tsuruta -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Xen-devel] dm-band: The I/O bandwidth controller: Performance Report
Hi, Ryo Tsuruta wrote: > The results of bandwidth control test on band-groups. > = > The configurations of the test #3: >o Prepare three partitions sdb5 and sdb6. >o Create two extra band-groups on sdb5, the first is of user1 and the > second is of user2. >o Give weights of 40, 20, 10 and 10 to the user1 band-group, the user2 > band-group, the default group of sdb5 and sdb6 respectively. >o Run 128 processes issuing random read/write direct I/O with 4KB data > on each device at the same time. you mean that you run 128 processes on each user-device pairs? Namely, I guess that user1: 128 processes on sdb5, user2: 128 processes on sdb5, another: 128 processes on sdb5, user2: 128 processes on sdb6. > Conclusions and future works > > Dm-band works well with random I/Os. I have a plan on running some tests > using various real applications such as databases or file servers. > If you have any other good idea to test dm-band, please let me know. The second preliminary studies might be: - What if you use a different I/O size on each device (or device-user pair)? - What if you use a different number of processes on each device (or device-user pair)? And my impression is that it's natural dm-band is in device-mapper, separated from I/O scheduler. Because bandwidth control and I/O scheduling are two different things, it may be simpler that they are implemented in different layers. Regards, Hiroya. > > Thank you, > Ryo Tsuruta. > > ___ > Xen-devel mailing list > [EMAIL PROTECTED] > http://lists.xensource.com/xen-devel > > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Xen-devel] dm-band: The I/O bandwidth controller: Performance Report
Hi, Ryo Tsuruta wrote: The results of bandwidth control test on band-groups. = The configurations of the test #3: o Prepare three partitions sdb5 and sdb6. o Create two extra band-groups on sdb5, the first is of user1 and the second is of user2. o Give weights of 40, 20, 10 and 10 to the user1 band-group, the user2 band-group, the default group of sdb5 and sdb6 respectively. o Run 128 processes issuing random read/write direct I/O with 4KB data on each device at the same time. you mean that you run 128 processes on each user-device pairs? Namely, I guess that user1: 128 processes on sdb5, user2: 128 processes on sdb5, another: 128 processes on sdb5, user2: 128 processes on sdb6. Conclusions and future works Dm-band works well with random I/Os. I have a plan on running some tests using various real applications such as databases or file servers. If you have any other good idea to test dm-band, please let me know. The second preliminary studies might be: - What if you use a different I/O size on each device (or device-user pair)? - What if you use a different number of processes on each device (or device-user pair)? And my impression is that it's natural dm-band is in device-mapper, separated from I/O scheduler. Because bandwidth control and I/O scheduling are two different things, it may be simpler that they are implemented in different layers. Regards, Hiroya. Thank you, Ryo Tsuruta. ___ Xen-devel mailing list [EMAIL PROTECTED] http://lists.xensource.com/xen-devel -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
