From: Mark Nelson <mark.nelson@inktank.com>
To: Kasper Dieter <dieter.kasper@ts.fujitsu.com>,
Sage Weil <sweil@redhat.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
"Somnath.Roy@sandisk.com" <Somnath.Roy@sandisk.com>,
Andreas Bluemle <andreas.bluemle@itxperts.de>,
"Allen.Samuels@sandisk.com" <Allen.Samuels@sandisk.com>,
"PVonStamwitz@us.fujitsu.com" <PVonStamwitz@us.fujitsu.com>,
"xinxin.shu@intel.com" <xinxin.shu@intel.com>,
"haomaiwang@gmail.com" <haomaiwang@gmail.com>,
"s.priebe@profihost.ag" <s.priebe@profihost.ag>,
"xiaoxi.chen@intel.com" <xiaoxi.chen@intel.com>,
"milosz@adfin.com" <milosz@adfin.com>,
"zhiqiang.wang@intel.com" <zhiqiang.wang@intel.com>,
"jianpeng.ma@intel.com" <jianpeng.ma@intel.com>,
"gdror@mellanox.com" <gdror@mellanox.com>,
"vuhuong@mellanox.com" <vuhuong@mellanox.com>,
"mark.nelson@inktank.com" <mark.nelson@inktank.com>
Subject: Re: Weekly performance meeting
Date: Thu, 25 Sep 2014 14:31:44 -0500 [thread overview]
Message-ID: <54246DA0.5050801@redhat.com> (raw)
In-Reply-To: <54246D6A.5060101@redhat.com>
Oops, replied to fast and meant to put Dieter! :)
Mark
On 09/25/2014 02:30 PM, Mark Nelson wrote:
> I'll be there too, and 100% agree with you Kasper! :)
>
> Mark
>
> On 09/25/2014 02:27 PM, Kasper Dieter wrote:
>> Hi Sage,
>>
>> I'm definitely interested in joining this weekly call starting Oct 1st.
>> Thanks for this initiative!
>>
>> Especially I'm interested in:
>> - how can we reduce the number of threads in the system
>> -- including to avoid the context switches in between
>> -- including to avoid the queues and locks in between
>> - how we can reduce the number of lines of code
>> -- including the multiple system calls for each IO
>> - how we can introduce a high efficient timestamp collection of the
>> most important FN check-points
>> (see for example the attached file)
>> to measure the change and effect of our actions
>>
>> Best Regards,
>> -Dieter
>>
>>
>> On Thu, Sep 25, 2014 at 08:27:00PM +0200, Sage Weil wrote:
>>> Hi everyone,
>>>
>>> A number of people have approached me about how to get more involved
>>> with
>>> the current work on improving performance and how to better coordinate
>>> with other interested parties. A few meetings have taken place offline
>>> with good results but only a few interested parties were involved.
>>>
>>> Ideally, we'd like to move as much of this dicussion into the public
>>> forums: ceph-devel@vger.kernel.org and #ceph-devel. That isn't always
>>> sufficient, however. I'd like to also set up a regular weekly meeting
>>> using google hangouts or bluejeans so that all interested parties can
>>> share progress. There are a lot of things we can do during the Hammer
>>> cycle to improve things but it will require some coordination of effort.
>>>
>>> Among other things, we can discuss:
>>>
>>> - observed performance limitations
>>> - high level strategies for addressing them
>>> - proposed patch sets and their performance impact
>>> - anything else that will move us forward
>>>
>>> One challenge is timezones: there are developers in the US, China,
>>> Europe,
>>> and Israel who may want to join. As a starting point, how about next
>>> Wednesday, 15:00 UTC? If I didn't do my tz math wrong, that's
>>>
>>> 8:00 (PDT, California)
>>> 15:00 (UTC)
>>> 18:00 (IDT, Israel)
>>> 23:00 (CST, China)
>>>
>>> That is surely not the ideal time for everyone but it can hopefully be a
>>> starting point.
>>>
>>> I've also created an etherpad for collecting discussion/agenda items at
>>>
>>> http://pad.ceph.com/p/performance_weekly
>>>
>>> Is there interest here? Please let everyone know if you are actively
>>> working in this area and/or would like to join, and update the pad above
>>> with the topics you would like to discuss.
>>>
>>> Thanks!
>>> sage
>
next prev parent reply other threads:[~2014-09-25 19:31 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 18:27 Weekly performance meeting Sage Weil
2014-09-25 19:03 ` Matt W. Benjamin
[not found] ` <20140925192728.GA22139@oder.mch.fsc.net>
2014-09-25 19:30 ` Mark Nelson
2014-09-25 19:31 ` Mark Nelson [this message]
2014-09-25 19:41 ` Sage Weil
2014-09-25 20:20 ` Somnath Roy
2014-10-01 9:30 ` Andreas Bluemle
2014-09-25 21:15 ` Vu Pham
2014-09-26 6:42 ` Dror Goldenberg
2014-09-26 1:50 ` Paul Von-Stamwitz
2014-09-26 2:27 ` Haomai Wang
2014-09-26 2:45 ` Haomai Wang
2014-09-26 6:30 ` Dong Yuan
2014-09-26 6:40 ` Somnath Roy
2014-09-26 7:20 ` Dong Yuan
2014-09-26 12:58 ` Milosz Tanski
2014-09-26 13:02 ` Christoph Hellwig
2014-09-26 15:37 ` Sage Weil
2014-09-26 15:57 ` Mark Nelson
2014-09-26 2:47 ` Guang Yang
2014-09-26 13:12 ` Mark Nelson
2014-09-27 3:05 ` Guang Yang
2014-09-26 6:40 ` Zhang, Jian
2014-09-26 7:25 ` Loic Dachary
2014-09-26 8:37 ` Zhang, Jian
2014-09-26 8:56 ` Loic Dachary
[not found] <549524118.380.1411702754627.JavaMail.root@thunderbeast.private.linuxbox.com>
2014-09-26 3:39 ` Matt W. Benjamin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54246DA0.5050801@redhat.com \
--to=mark.nelson@inktank.com \
--cc=Allen.Samuels@sandisk.com \
--cc=PVonStamwitz@us.fujitsu.com \
--cc=Somnath.Roy@sandisk.com \
--cc=andreas.bluemle@itxperts.de \
--cc=ceph-devel@vger.kernel.org \
--cc=dieter.kasper@ts.fujitsu.com \
--cc=gdror@mellanox.com \
--cc=haomaiwang@gmail.com \
--cc=jianpeng.ma@intel.com \
--cc=milosz@adfin.com \
--cc=s.priebe@profihost.ag \
--cc=sweil@redhat.com \
--cc=vuhuong@mellanox.com \
--cc=xiaoxi.chen@intel.com \
--cc=xinxin.shu@intel.com \
--cc=zhiqiang.wang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox