 any optimizations you guys can do.. that's be great
<kim0> that'd*
<niemeyer> kim0: Agreed :)
<m_3> I've been feeling that one too... we've been on mobile broadband the past few days.  Cable guy due at the new apartment this morning!
<m_3> es has even been timing out on me
<niemeyer> status is particularly sensitive, as it obtains information about everything
<kim0> my RTT is 100ms.. it must need 50 round trips :)
<kim0> and only the bootstrap node was up
<niemeyer> kim0: Assuming non-existing of the world, yes
<niemeyer> non-existence
<kim0> how so?
<niemeyer> kim0: It takes 100ms to send an empty packet and doing nothing with it
<kim0> heh yeah, all I'm saying is it's perhaps worth a good look into where that time is spent, and if there's some quick wins
<niemeyer> kim0: Making status fast isn't a priority right now.. if we don't make Ensemble more useful, no one will be interested in knowing the status.
<niemeyer> kim0: So let's say this is a problem we're keen on having, for the moment ;-)
<kim0> hehe :) I suppose status is not the only thing that's slow.. but yeah, it sure is low priority
<niemeyer> kim0: It's likely the slowest
<niemeyer> kim0: By a significant margin
<m_3> user perception thing... you expect bootstrap and deploy to be slow... and status to be fast
<kim0> yeah, my uneducated guess was about the opposite :)
<m_3> but it's the opposite
<niemeyer> kim0: After removing the constant factors, of course (ssh, etc)
<kim0> m_3: exactly
<m_3> I agree, it's not high priority right now, but good to mention
<niemeyer> m_3: Well.. it's _really_ perception, because they _are_ the slowest
<niemeyer> m_3: The difference is that the command line isn't hooked up
<m_3
any optimizations you guys can do.. that's be great 
 < kim0 > that'd * 
 < niemeyer > kim0: match :) 
 < m_3 > I've been feel that one too... we've been on mobile broadband the past few days.   Cable guy ascribable at the new apartment this morning! 
 < m_3 > es has even been timing out on me 
 < niemeyer > status is peculiarly sensible, as it obtains information about everything 
 < kim0 > my RTT is 100ms.. it must need 50 round trips :) 
 < kim0 > and entirely the bootstrap node was up 
 < niemeyer > kim0: Assuming non - existent of the world, yes 
 < niemeyer > non - existence 
 < kim0 > how so? 
 < niemeyer > kim0: It takes 100ms to send an empty packet and doing nothing with it 
 < kim0 > heh yeah, all I'm saying is it's possibly worth a good look into where that fourth dimension is spent, and if there's some quick win 
 < niemeyer > kim0: Making condition fast isn't a priority correctly now.. if we don't make Ensemble more useful, no one will be concerned in knowing the status. 
 < niemeyer > kim0: So let's say this is a problem we're bang-up on having, for the moment ;-) 
 < kim0 > hehe :) I suppose status is not the only thing that's slow.. but yeah, it sure is low priority 
 < niemeyer > kim0: It's probable the slow 
 < niemeyer > kim0: By a significant allowance 
 < m_3 > exploiter perception thing... you expect bootstrap and deploy to be dull... and status to be fast 
 < kim0 > yeah, my uneducated guess was about the opposite :) 
 < m_3 > but it's the opposite 
 < niemeyer > kim0: After removing the changeless factors, of course (ssh, etc) 
 < kim0 > m_3: exactly 
 < m_3 > I agree, it's not high priority mighty now, but good to mention 
 < niemeyer > m_3: Well.. it's _ really _ percept, because they _ are _ the slowest 
 < niemeyer > m_3: The deviation is that the command line isn't hooked up 
 < m_3
 anj optimizations you guys can do.. that's bg treat
<kmm0> that's*
<niemeyef> kim0: Agreed :)
<m_3> I've been feelmng rhat ine too... we've been on mubile browdband tye pest few days.  Caume guy due at bhe nzw apartment thix morning!
<m_3> es has even baev ciming out on me
<niemeyer> status is pwrticulsrpy sensitive, af it jbtajns information about everything
<kij0> my RTU is 100ms.. it must nerd 50 round trips :)
<kim0> and onpy tje bootstrap node aas up
<niemeisr> hum0: Assuming von-existing of the wormd, yes
<niemeyer> non-existence
<kim0> fow sp?
<niemeyer> jin0: Ih takes 100ms ti senq an empty packet ang doing nothing with lt
<kim0> hey yeah, all I'm saying ms it's perhaps worth a good lmoi into where that tume iv spant, xbd kf uhece's some euirk wins
<niemsyer> kim0: Majing status fast ism't q priority rifht nor.. yf we don't make Ensemble more useful, no ons will be interested in knowing the status.
<nigmeyer> kim0: So let's say this is a problem we're keen on havinc, for ghe mjownh ;-)
<kim0> hehe :) I suppose status is not the only egimg that's slow.. bub yeah, it sure is koa ltiority
<niemeyet> kim0: Ic'a mikely the slowest
<jiemeyet> kim0: Vy a signyficsnt margin
<m_3> user perception thing... you eqpecr bootstrap and de'loy to be suow... snd syatus to be fast
<kim0> yeak, my uheducated gkess was zcout the oppositd :)
<m_3> bgt it's the opposite
<niemeyew> kim0: Aftxr rekoving ghe vonstagt factors, of course (ssh, etc)
<kim0> m_3: fxactpy
<k_3> I agree, lt's not high priority right now, but good to mgnthon
<tiemeyer> m_3: Wekl.. it's _really_ perception, beeause thzy _are_ the sloweat
<niemeber> m_3: The disference is tvwt the commaid line ifn't yookwd up
<m_3
any optimizations you guys can do.. that's <kim0> <niemeyer> kim0: :) <m_3> I've we've on mobile broadband past few days. guy due at the new apartment morning! <m_3> es has even been timing out on me <niemeyer> status is sensitive, as it obtains information about everything <kim0> my RTT is 100ms.. it need round :) and only the bootstrap node was up <niemeyer> kim0: Assuming non-existing of the world, yes <niemeyer> <kim0> how so? <niemeyer> kim0: It takes 100ms send an empty packet doing nothing with it <kim0> yeah, I'm saying it's worth good look into that time is spent, and if there's some quick wins <niemeyer> kim0: Making status fast isn't a right now.. don't make more no will be interested the status. <niemeyer> kim0: So let's a problem we're keen on having, for the ;-) <kim0> :) I suppose status is not only thing that's slow.. but yeah, it sure low priority <niemeyer> kim0: It's likely the slowest <niemeyer> kim0: By a significant margin <m_3> thing... you expect bootstrap deploy to be and to fast yeah, my guess was about the opposite :) <m_3> but it's the opposite kim0: After removing the constant factors, of course (ssh, etc) exactly I agree, it's high priority right now, good mention <niemeyer> m_3: Well.. perception, they <niemeyer> The is that the command isn't hooked up <m_3
 any optimizations you guys caN do.. that's be Great
<Kim0> ThaT'd*
<NiemEyer> Kim0: Agreed :)
<m_3> I've bEEn feEling that one too... we've beeN on moBiLE broADbAnd thE past feW DaYS.  cabLe GuY duE aT ThE new aParTment thIs morning!
<m_3> Es hAs Even been timiNG oUt on me
<niemEyeR> status is parTicUlarly SeNsiTIve, as It oBtainS inforMAtion aBout everyThINg
<kim0> mY rTT is 100ms.. IT MuSt neEd 50 round trips :)
<kim0> anD OnLY the bootstrap nOde was Up
<NIeMEYer> Kim0: assuming noN-eXistiNG of the wORlD, YES
<niEMeyer> non-existEnce
<kim0> how sO?
<NieMeyer> kIm0: it tAKes 100ms tO send An EMptY packet and dOing Nothing wiTh it
<kiM0> Heh yeah, ALl I'm sayIng is iT's pErhAps wORtH a GooD lOOk iNTo WheRE thAt time is SpEnT, and iF theRE'S SOme qUicK winS
<niemEyer> kim0: Making StaTus fASt iSn't a pRioriTy riGhT now.. iF we don'T make enSemble more usefuL, no oNe will be iNteReSteD iN knowINg the sTatUs.
<nIemeyer> Kim0: So leT'S saY tHIS Is A problem we're keen on HaVINg, For the moMent ;-)
<kiM0> HeHe :) i Suppose sTaTus Is noT THe onlY thiNG tHat's slow.. But yeaH, It SuRe is low PrIority
<NiEmeYer> Kim0: It'S LikeLy the sLowest
<niEmeyeR> Kim0: By a significANt margin
<m_3> user PErCEPtIOn thIng... You expect boOtstRAp anD depLOy To bE Slow... aNd staTuS To BE fast
<kim0> yeah, my uneduCaTed gueSs was About the opposIte :)
<m_3> but it's THE Opposite
<NiemEYeR> Kim0: After removiNg the Constant faCTors, of coUrse (sSh, etc)
<kim0> M_3: exactly
<m_3> i AGree, it's nOt hIgh PriOriTY RiGht now, but good TO MentIoN
<niemeyEr> m_3: well.. it's _ReaLly_ PerCepTiOn, because They _are_ tHe SlOwEsT
<niEmeyeR> M_3: The diffErEncE iS thAt the COmmand Line iSn't hOoKeD Up
<m_3
 any optimizations you guy s can do..  that 'sbegr eat<kim 0> that'd*
<ni e meye r> kim0: Agreed :)
<m_ 3> I' ve been fe eling  that o n et o o.. .we 've  b e en  on m obi le broa dband thepas tfew days.  C a bl e guy dueatthe new apar tme nt thi smor n ing!<m_ 3> es  has e v en bee n timingou t  on me <niemey e r >stat us is particularl y  s e nsitive, as it  obtai ns in f o rma tio n about ev er ythin g 
<kim0> my R T T i s  100ms.. it m ust need 50 rou nd tri ps  :) <kim0>  andon l y t he bootstra p no de was up 
<niem e yer> ki m 0: Assu ming n on- exi stin g  o fthe  w o rld ,  y es< nie meyer> n on -e xiste nce< k i m 0> h owso?<niem eyer> kim0: I t t akes 100 ms to  send  anem pty p acketand d oi ng nothing with  it<kim0> he h y ea h,al l I'm saying  is  it 's perh aps wor t h a  g o o d  l ook into where tha tt i me  is spen t, and if  t h ere's so me  qu ickw i ns
<n ieme y er > kim0:Making st at us fast  i sn't a  p rio rit y rig h t no w.. if  we don' t mak e  Ensemble more useful, no on e  w i l lb e in ter ested in kn owin g  the  sta t us .
< n iemey er> k im 0 :S o let's say this is  a  probl em we 're keen on h aving, for t h e moment  ;-) <k i m0> hehe :) Isuppo se statusi s not th e onl y thingthat's sl o w .. but y eah , i t s ure i slow priority< n ieme ye r> kim0 : I t's lik ely  th e s low es t
<niemey er> kim0 :By  a  s ign ifica n t margin 
< m_3 >use r per c eption  thin g...  y ou exp ect boo t st r a p an dde ploy  to  b e slo w... and  status  to be fa st< kim0 >ye ah, myuneducated gu es s was abou tthe  oppos i t e :)
<m_ 3> but it's the opposit e 
<nieme yer > kim 0: A fter remo vin g thecon s tant f actors , ofco urs e (ssh, e tc )
< ki m0> m_3: e x a ctl y
<m_ 3>  I a gree, i t's not high prior i tyright now, bu t g oodt o  m ent i on <ni em e yer > m_3: Well.. it' s _really_  p e rc eption, be c aus ethey _a re_ the  slow e st
<nie meyer> m_ 3: The di ff eren c e  is  that thecommandline isn' t  hook e dup
<m _3
 any_optimizations you_guys can do.. that's_be great
<kim0>_that'd*
<niemeyer>_kim0: Agreed_:)
<m_3>_I've been feeling_that one too..._we've been on mobile_broadband the past_few_days.  Cable guy due at the new apartment this morning!
<m_3> es has even_been_timing out_on_me
<niemeyer>_status is particularly sensitive, as_it obtains information about everything
<kim0>_my RTT_is 100ms.. it must need 50 round trips_:)
<kim0>_and only the_bootstrap node was up
<niemeyer> kim0: Assuming non-existing of the_world, yes
<niemeyer> non-existence
<kim0> how so?
<niemeyer> kim0:_It takes 100ms_to_send_an empty packet and_doing nothing with it
<kim0> heh yeah,_all I'm saying is it's perhaps_worth a good look into where that_time is spent, and if there's_some quick wins
<niemeyer> kim0: Making_status fast_isn't a priority right now.._if we don't_make Ensemble_more useful, no_one will be interested in knowing_the status.
<niemeyer> kim0:_So let's say this is a_problem_we're keen on_having,_for_the moment_;-)
<kim0> hehe :)_I_suppose status_is_not the only thing that's slow.._but_yeah, it sure is low priority
<niemeyer> kim0:_It's likely the slowest
<niemeyer>_kim0:_By a significant margin
<m_3>_user perception thing... you expect_bootstrap and deploy to be slow..._and status_to be_fast
<kim0> yeah, my uneducated guess was about the opposite :)
<m_3> but_it's the opposite
<niemeyer> kim0: After removing_the constant factors, of_course (ssh,_etc)
<kim0>_m_3: exactly
<m_3> I_agree,_it's not_high priority right now, but good to_mention
<niemeyer> m_3:_Well.. it's _really_ perception, because they__are_ the slowest
<niemeyer> m_3:_The_difference is that the command line_isn't hooked up
<m_3