Thursday, 2015-11-12

*** Paco has joined #openstack-performance02:21
*** Paco has left #openstack-performance02:25
*** Paco has joined #openstack-performance02:31
*** arnoldje has joined #openstack-performance03:24
*** sw3 has joined #openstack-performance03:52
*** badari has quit IRC04:17
*** badari has joined #openstack-performance04:22
*** pengzh has joined #openstack-performance05:31
*** pengzh has quit IRC05:32
*** arnoldje has quit IRC05:38
*** david-bravo23 has quit IRC06:00
*** Paco has quit IRC08:42
DinaBelovaharlowja_, kun_huang, SpamapS - hehe, I felt asleep last night too early :) good discussion :)08:45
DinaBelovafolks, btw I'm really encouraging you to add your content to the https://wiki.openstack.org/wiki/Meetings/Performance next meeting agenda :)08:47
DinaBelovait was a complain that it was too short timeframe last time :)08:47
*** Paco has joined #openstack-performance08:49
*** amaretskiy has joined #openstack-performance09:32
boris-42DinaBelova: btw10:02
boris-42DinaBelova: I am not sure that we should have separated chat for osprofiler10:02
boris-42DinaBelova: however I created it already10:02
boris-42openstack-osprofiler10:02
boris-421 year ago=)10:02
DinaBelovaboris-42 :D10:03
DinaBelovawell, personally I'll prefer to chat here about it10:03
DinaBelovaas interested people will be here :)10:03
DinaBelovaI suppose that at least :)10:03
boris-42DinaBelova: btw https://review.openstack.org/#/c/242168/10:03
DinaBelovaboris-42 - yep, saw that10:04
boris-42DinaBelova: I would put on title: "Dead of scalability"10:04
DinaBelovamost probably issues will be faced for sure... although that was logical step that would have been done for sure. The thing is to fix all issues10:04
DinaBelovanot  try to write something else once that will be clear there are bugs :)10:05
DinaBelovaboris-42 - I've started working on https://github.com/openstack/osprofiler/blob/master/doc/specs/in-progress/multi_backend_support.rst10:07
DinaBelovaand fixed your comment on https://review.openstack.org/#/c/244084/10:07
DinaBelovakun_huang, SpamapS, harlowja_  - btw, performance team inside Mirantis is currently working on creating the template to publish our performance test plans. I hope something will be available in human-readable way next week and I'll share it10:09
DinaBelovaand I10:11
DinaBelovawill ask all of you guys here to review them, propose your own ideas, etc.10:11
DinaBelovawe'll try to perform them in life as well10:11
boris-42DinaBelova: that one spec is quite hard10:30
DinaBelova@boris-42 - yep, I see that.. I think I'll start with drivers directory creation and adding Ceilometer there10:31
DinaBelovawell, at least I may start :)10:31
boris-42DinaBelova: btw current ceilometer backend is broken10:32
DinaBelovaboris-42 - sh*t, I forgot about it10:32
DinaBelovaboris-42 - well, I'll start with its fixing I guess10:33
boris-42DinaBelova: ok =)10:35
boris-42DinaBelova: I will cut now 0.3.1 version10:36
DinaBelovaack10:36
DinaBelova@boris-42 - although I suppose after ceilo backend fixing that should be done once more time?10:38
boris-42DinaBelova: we can cut releases even every day =)10:41
DinaBelova:D10:41
boris-42DinaBelova: so I will cut 0.3.110:41
DinaBelovaack10:41
boris-42DinaBelova: and I will make patch in global requriemnts10:41
boris-42DinaBelova: to force everywhere osprofiler >= 0.3.110:42
DinaBelovaok, cool10:42
DinaBelovaafter that I can make changes to Cinder, Trove, etc.10:42
boris-42DinaBelova: after that you or me or somebody else will be able to fix everything10:42
boris-42DinaBelova: yep10:42
DinaBelovaok, cool10:42
boris-42DinaBelova: new release is here https://github.com/openstack/osprofiler/releases10:45
DinaBelovaok, give me please a link to the requirements as well10:45
DinaBelova@boris-42 ^^10:45
boris-42DinaBelova:  https://review.openstack.org/24454310:48
DinaBelovathank10:48
*** Paco has quit IRC11:11
*** mwagner has quit IRC11:34
*** ozamiatin has joined #openstack-performance11:38
*** badari has quit IRC11:45
*** ozamiatin has quit IRC11:49
*** ozamiatin has joined #openstack-performance12:44
*** mwagner has joined #openstack-performance13:09
*** rvasilets has joined #openstack-performance13:20
*** ozamiatin has quit IRC13:25
*** ozamiatin has joined #openstack-performance13:27
*** ozamiatin has quit IRC13:37
*** ozamiatin has joined #openstack-performance13:41
*** boris-42 has quit IRC13:48
*** andreykurilin has left #openstack-performance14:01
*** andreykurilin has joined #openstack-performance14:02
*** arnoldje has joined #openstack-performance14:21
*** regXboi has joined #openstack-performance14:30
*** badari has joined #openstack-performance14:43
*** arnoldje has quit IRC15:03
*** arnoldje has joined #openstack-performance15:22
*** rvasilets has quit IRC15:40
*** mdorman has joined #openstack-performance15:57
*** mdorman has quit IRC16:38
*** ozamiatin has quit IRC16:38
*** mwagner has quit IRC16:41
*** mdorman has joined #openstack-performance16:42
*** rmart04 has joined #openstack-performance17:16
*** mwagner has joined #openstack-performance17:20
*** rmart04 has quit IRC17:21
*** rmart04 has joined #openstack-performance17:21
*** rmart04_ has joined #openstack-performance17:26
*** rmart04 has quit IRC17:28
*** rmart04_ is now known as rmart0417:28
*** amaretskiy has quit IRC17:50
*** serverascode has joined #openstack-performance18:43
*** markvoelker has joined #openstack-performance18:45
*** rmart04 has quit IRC18:47
*** klindgren__ has joined #openstack-performance18:48
*** klindgren__ is now known as klindgren18:48
klindgrenDinaBelova, has Miratnis been able to duplicate remote conductor melting cores in medium sized envs (200+ HV's)?18:49
*** jproulx1 has joined #openstack-performance18:49
harlowja_melt some marshmallows on the melting cores18:50
harlowja_and make smores18:51
*** mgagne has joined #openstack-performance18:53
*** mdorman has quit IRC18:58
*** mdorman has joined #openstack-performance18:59
harlowja_klindgren perhaps we should start making an etherpad (or something) just about this issue?19:01
harlowja_centralizing all the different etherpads where it has been discussed ---> one etherpad19:01
harlowja_(less scattered info ftw)19:02
harlowja_SpamapS maybe falling over isn't the right word, 'melting cores' might be better, lol19:16
harlowja_klindgren loves the melting cores, lol19:16
SpamapSif it really is just pegging CPUs, that definitely points at unoptimized encapsulation.19:17
SpamapSTalking to rabbit is not CPU bound19:17
SpamapSso....?19:17
klindgrenwe run conductor with 20 workers, typically they are running between 8-55% cpu per Conductor worker19:19
klindgrentypically seems to be ~20% cpu per conductor worker19:20
klindgrensame box also runs rabbitmq - typically consuming ~200-300% cpu19:21
klindgrenand thats basically on an idle system with ~250 hv's19:22
klindgrenstart doing deployments and conductor use jumps pretty high19:22
klindgrenWe also have 3 of these servers running conductor - all will peg out cpu19:23
*** wootehfoot has joined #openstack-performance19:29
*** wootehfoot has quit IRC19:29
harlowja_:-/19:41
harlowja_so 3 servers running conductor * 20 == 60 conductor processes19:42
harlowja_klindgren thats accurate right?19:42
*** rmart04 has joined #openstack-performance19:51
*** ozamiatin has joined #openstack-performance19:57
*** arnoldje has quit IRC20:03
klindgrenharlowja_, yep20:03
klindgrenit use to be 40 conductor processes each20:04
klindgrenbut at we kept tripping 100% of all cores utilized for a period > 4 minutes alarms20:04
klindgrenso we dropped it down a little bit to ease the alarms we were seeing for those hosts20:05
klindgrenbecause we like sleep20:05
klindgrenbut I am noticing frequent Model server went away errors across HV's so I am tempted to increase the number of workers to see if that drops off20:06
*** rmart04 has quit IRC20:06
*** ozamiatin has quit IRC20:06
*** arnoldje has joined #openstack-performance20:19
DinaBelovaklindgren - nope, we did not have the opportunity to spend time on his particular issues yet. although it is in our plans due to the importance of this problem20:23
DinaBelovaklindgren - may you please create the etherpad with all details of your particular situation? this will be *VERY* helpful20:26
DinaBelovaklindgren - this point will be one of the topic on the next meeting20:34
DinaBelovaI suppose I'll check when Mirantis can work on this before Tuesday20:34
*** arnoldje has quit IRC20:42
*** arnoldje has joined #openstack-performance21:07
*** mikal has joined #openstack-performance21:31
*** HenryG has joined #openstack-performance21:36
*** harshs has joined #openstack-performance22:05
*** mdorman has quit IRC22:06
*** regXboi has quit IRC22:15
*** boris-42 has joined #openstack-performance22:19
klindgrenDinaBelova, https://etherpad.openstack.org/p/remote-conductor-performance - Unsure what you else you need.  Like we said aside from adding some more hardware and tuning some workers - we haven't really dug in.22:45
*** arnoldje has quit IRC22:54
*** redixin has quit IRC22:54
*** mdorman has joined #openstack-performance22:58
harlowja_thx klindgren23:07
*** harshs has quit IRC23:56

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!