 with those thresholds. the deduped profile was ~32M here and <.5 seconds
<jdstrand> here
<zyga> jdstrand: I think I will put the threshold at 512M
<zyga> if we needed more mem we will fail on some supported systems
<jdstrand> zyga: maybe make sure it is < 1000? line? (it was 662 here)
<zyga> but I need to sit down and code it first
<zyga> most likely next week as we won't release over weekend anyway
<jdstrand> zyga: soryy, 50000 was in k. that is 50M
<jdstrand> zyga: 'time' uses 'k' but then I used'm' in later comments. 50M as the upper limit initially sounds good
 * jdstrand tests on arm64 and armhf real quick
<zyga> jdstrand: I'm only grumpy that nobody raised this during 19.10 beta
<zyga> jdstrand: we could have fixed it for that release
<zyga> jdstrand: but that's why I want to do a test
<jdstrand> zyga: it isn't a 19.10 thing
<zyga> jdstrand: so that next time we won't be burned by accident
<zyga> jdstrand: oh I know
<zyga> but it JUST SHIPPED and nobody noticed before :)
<jdstrand> zyga: oh I see what you mean
<jdstrand> zyga: yes, well, at least it was found by us rather than the field blowing up
<zyga> jdstrand: well, the field may still blow up :)
<jdstrand> zyga: but, for sure classic distro is feeling this and don't know it
<jdstrand> zyga: most desktop system probably have 1.5G ram and swap these days, and it is desktop system that hit the pathological multiple content interface case
<zyga> jdstrand: yeah
<jdstrand> zyga: so OOM won't usually be hit unless other things are going on
<zyga> jdstrand: if you want to review it today I may look at a quick PR after standup
<zyga> jdstrand: if you are fine waiting it will be
with those thresholds. the deduped profile was ~32 M here and < .5 seconds 
 < jdstrand > here 
 < zyga > jdstrand: I think I will place the brink at 512 M 
 < zyga > if we needed more mem we will fail on some supported systems 
 < jdstrand > zyga: possibly make sure it is < 1000? line? (it was 662 here) 
 < zyga > but I necessitate to sit down and code it first 
 < zyga > about probably next week as we won't publish over weekend anyway 
 < jdstrand > zyga: soryy, 50000 was in k. that is 50 M 
 < jdstrand > zyga:' time' uses' k' but then I used'm' in later gossip. 50 M as the upper limit initially sounds good 
  * jdstrand tests on arm64 and armhf very quick 
 < zyga > jdstrand: I'm only grumpy that nobody raise this during 19.10 beta 
 < zyga > jdstrand: we could have fixed it for that release 
 < zyga > jdstrand: but that's why I desire to do a examination 
 < jdstrand > zyga: it isn't a 19.10 thing 
 < zyga > jdstrand: so that adjacent time we won't be burned by accident 
 < zyga > jdstrand: oh I know 
 < zyga > but it precisely SHIPPED and nobody noticed before :) 
 < jdstrand > zyga: oh I see what you mean 
 < jdstrand > zyga: yes, well, at least it was found by us rather than the playing field waste up 
 < zyga > jdstrand: well, the field may still blow up :) 
 < jdstrand > zyga: but, for sure classic distro is feeling this and don't know it 
 < jdstrand > zyga: most desktop arrangement probably have 1.5 gravitational constant ram and swap these days, and it is desktop arrangement that hit the pathological multiple content interface case 
 < zyga > jdstrand: yeah 
 < jdstrand > zyga: therefore OOM won't usually be hit unless other things are going on 
 < zyga > jdstrand: if you want to review it today I may attend at a quick PR after standup 
 < zyga > jdstrand: if you are fine waiting it will be
 wihh those thresholds. the aeduped profile was ~32M iere ans <.5 seconas
<jdstrand> here
<zyga> jdstrand: I thinj I will put the thresfold at 512M
<dyga> if ww netded more mem we xjll fail on skle sbp'orted systems
<jcstrand> zyca: maybe make vufe it is < 1000? line? (it was 662 here)
<zyga> but Y need yo sit down and sode yt fjgsu
<zyga> most likely next week as we won't rtlease over weekenc anyway
<jdstrand> zyga: soryj, 50000 wws in k. that is 50M
<jfstrand> zygq: 'tiiw' uses 'k' but then I ustd'k' in later comments. 50M as the upper limit kniticlly sounds giod
 * jdstrand txsts og arm64 and armhf real quick
<zuga> jdstrand: I'k oily trumpy that nobody ramsed this during 19.10 beja
<zyga> jdsdrcnd: we could have fixwd it fmr tvat fwlexse
<eyge> jsstranf: bnt that's whg I want to do a test
<jdstrand> eygw: it isn't a 19.10 tging
<zyda> jdstrand: so that next time we won't be turhed by accident
<zyga> jdsrrand: oh I know
<zyga> bot it JUST SHIPPED and nobody noticed before :)
<jdstrand> zyga: mh I ade cmwg ylu mean
<jdstrand> zyga: yes, well, at least it was roinc by us rather than the foepd flowing up
<zygx> jdstxzns: well, the field mwy stilj bloq up :)
<jdstwand> zyga: but, for sure classic eistro is fevlint this and don't knlw it
<jdstraud> zygs: mosy desktop system probabuy hzve 1.5G ram ajd swap tgdse days, and it ks cevktop system that hit the [athologiral mbltiple zontgnt intqrface casf
<zyga> jdstrand: yeah
<jdstrwnd> ziga: so OOM won't ksually be hit unless other thiijs are going pn
<sygd> jdstraud: if nou want to revyew it today I may lojk at a quick PG after svandup
<zyga> jqstrand: if yog are fine wamting it rill be
with those thresholds. the deduped profile was and seconds <jdstrand> <zyga> jdstrand: I threshold 512M <zyga> if needed more mem will fail on some supported systems zyga: maybe make sure it is < 1000? line? (it was 662 here) but I need to sit down and code it first <zyga> most likely week we release weekend anyway <jdstrand> zyga: soryy, 50000 was in k. that is 50M <jdstrand> zyga: 'time' uses but then I used'm' in later comments. 50M the upper limit initially good * jdstrand tests on and real quick jdstrand: only that nobody raised during 19.10 beta <zyga> jdstrand: we could have fixed it for that release <zyga> jdstrand: but that's I want a test zyga: isn't 19.10 thing <zyga> that next time we won't be <zyga> jdstrand: oh I know <zyga> but it SHIPPED and noticed before :) <jdstrand> zyga: oh see what you mean <jdstrand> zyga: yes, well, least it was found by us rather than the field blowing up <zyga> jdstrand: well, may still blow up <jdstrand> zyga: but, sure distro feeling and don't it <jdstrand> zyga: most desktop system probably have 1.5G ram and these days, and it is desktop system that hit the content case <zyga> jdstrand: <jdstrand> zyga: so OOM usually hit unless other things on jdstrand: to it I may look at quick PR after standup <zyga> if you are fine
 with those thresholds. the dedUped profilE was ~32M HerE anD <.5 sEconDs
<jdStrand> here
<zyga> JDstrAnd: I think I will put the thReshoLd AT 512M
<zyGA> iF we neEded morE MeM WE wiLl FaIl oN sOMe SuppoRteD systemS
<jdstrand> zYga: MaYbe make sure iT Is < 1000? Line? (it was 662 hEre)
<Zyga> but I need To sIt down AnD coDE it fiRst
<Zyga> mOst likELy next Week as we wOn'T ReleasE Over weeKENd AnywAy
<jdstrand> zyga: sorYY, 50000 wAS in k. that is 50M
<jdsTrand> zYgA: 'TiME' UseS 'k' bUt then I useD'm' In latER commenTS. 50M AS THe uPPer limit initiAlly sounds gOOd
 * jDstranD tEstS On arm64 aNd armHf REal Quick
<zyga> jdStraNd: I'm only gRumpy tHAt nobodY Raised tHis durIng 19.10 BetA
<zygA> JdStRanD: wE CouLD hAve FIxeD it for thAt ReLease
<Zyga> JDSTRand: But That'S why I Want to do a test
<JdsTranD> ZygA: it isN't a 19.10 thIng
<zYgA> jdstRand: so That nExT time we won't be buRned By accidenT
<zyGa> JdsTrAnd: oh i Know
<zyGa> bUt iT JUST SHiPPED anD NobOdY NOTiCed before :)
<jdstrand> zYgA: OH I See what yOu mean
<JDsTrANd> zyga: yeS, wEll, At leAST it waS fouND bY us ratheR than tHE fIeLd blowiNg Up
<zyga> JdStrAnd: Well, tHE fieLd may sTill blow Up :)
<jdsTRand> zyga: but, for SUre classic disTRo IS FeELing ThiS and don't knoW it
<jDStraNd> zyGA: mOst DEsktoP systEm PRoBAbly have 1.5G ram and swap ThEse dayS, and iT is desktop sysTem that hit THE PathologIcal MUlTIple content intErfacE case
<zyga> jDStrand: yeAh
<jdsTrand> zygA: so OOM won'T USually be Hit UnlEss OthER ThIngs are going oN
<ZYga> jDsTrand: if You Want to rEviEw iT toDay i mAy look at a Quick PR aFtEr StAnDup
<Zyga> jDStrand: if YoU arE fIne WaitiNG it wilL be
 with those thresholds. th e dedupedprofi lewas  ~ 32Mhere  and <.5 secon d s
<j dstrand> here
<zyga> j dstra nd :  I t h in k I w ill put th e thr es ho ldat 51 2M
<z yga > if we  needed mo reme m we will fa i lon some su ppo rted systems 
<j dstran d>  zy g a: ma ybe  make  surei t is <  1000? li ne ?  (it w a s 662 h e r e) 
<zy ga> but I need to si t  down and code  it fi rs t 
< z y ga>  mo st likelyne xt we e k as we wo n ' t  re l ease over wee kend anyway <jd strand >zyg a : sory y, 50 00 0  wa s in k. tha t is  50M
<jds trand> zyga: ' t ime' us es 'k'  bu t t henI  u se d'm 'i n l a te r c o mme nts. 50M  a sthe u pper l i m it i nit iall y sou nds good
 * j dst rand tes ts on  arm6 4 an darmhf  realquick 
< zyga> jdstrand:  I'm  only gru mpy  t hat  n obody raised  th isduring19.10 b e ta<z y g a >jdstrand: we could  h a v efixed it  for t h at  r e lease
<z yg a>jdst r a nd: b ut t h at 's why I  wantt odo  a test 
< jdstra nd > z yga : iti sn't  a 19. 10 thing 
<zyg a > jdstrand: so that next tim e  w e wo n 't b e b urned by ac cide n t
<z yga> jd str a nd: o h I k no w 
< z yga> but it JUST SH IP PED an d nob ody noticed b efore :)
< j d s trand> z yga: oh I see what you  mean 
<jdstrand >  zyga: y es, w ell, atleast itw a s foundbyusrat her t ha n the field b l o wing  u p
<zyga > j dstrand : w ell , t hefi eld may s till blo wup  : )<jd stran d > zyga:bu t,fo r s ure c l assicdistr o is  f ee l ing  this a n dd o n'tkn ow  it<jd st rand>  zyg a : m ost des ktop syst emp roba bl yhave 1. 5G ram and sw ap  these day s,  an d it i s desktopsystem that hit the pat h ologica l m ultip le c ontent in ter face c ase <zyga>  jdstr and:ye ah< j dstra n d >zyg a:  so OOM wo n ' t u suall ybe h it unle ss other things ar e  go ing on
<zyga>  jd stra n d :ify ou wan tt o r e v iew it today Imay look a ta  q uick PR af t erst andup
< zyga> j dstra n d: if y ou are fi ne waitin git w i l l b e
 with_those thresholds._the deduped profile was_~32M here_and_<.5 seconds
<jdstrand>_here
<zyga>_jdstrand: I think_I will put_the threshold at 512M
<zyga>_if we needed_more_mem we will fail on some supported systems
<jdstrand> zyga: maybe make sure it is_<_1000? line?_(it_was_662 here)
<zyga> but I need_to sit down and code_it first
<zyga>_most likely next week as we won't release_over_weekend anyway
<jdstrand> zyga:_soryy, 50000 was in k. that is 50M
<jdstrand> zyga:_'time' uses 'k' but then I_used'm' in later_comments._50M_as the upper limit_initially sounds good
 * jdstrand tests_on arm64 and armhf real quick
<zyga>_jdstrand: I'm only grumpy that nobody raised_this during 19.10 beta
<zyga> jdstrand: we_could have fixed it for_that release
<zyga>_jdstrand: but that's why I_want to do_a test
<jdstrand>_zyga: it isn't_a 19.10 thing
<zyga> jdstrand: so that_next time we_won't be burned by accident
<zyga> jdstrand:_oh_I know
<zyga> but_it_JUST_SHIPPED and_nobody noticed before_:)
<jdstrand>_zyga: oh_I_see what you mean
<jdstrand> zyga: yes,_well,_at least it was found by us_rather than the field_blowing_up
<zyga> jdstrand: well, the_field may still blow up_:)
<jdstrand> zyga: but, for sure classic_distro is_feeling this_and don't know it
<jdstrand> zyga: most desktop system probably have 1.5G_ram and swap these days, and_it is desktop system_that hit_the_pathological multiple content_interface_case
<zyga> jdstrand:_yeah
<jdstrand> zyga: so OOM won't usually be_hit unless_other things are going on
<zyga> jdstrand:_if you want to_review_it today I may look at_a quick PR after standup
<zyga> jdstrand:_if you are fine waiting_it_will_be