[00:18] JAAS has been really sluggish from the cli the last few days [00:18] `juju models` and `juju status` seems to take forever [00:19] more like 10 seconds [00:19] do others experience something similar? [13:48] bdx: hmm, not messed with it over the weekend. Will see. [14:21] rick_h: I'm finding `juju models` to be super laggy [14:22] 5-10-20 secs [14:29] bdx: is it doing it now? [14:30] bdx: it seems fast for me but I've recently cleaned up my models. 2.0s total [14:30] rick_h: yea [14:30] bdx: can you screencapture running it with --debug to see if something jumps out as hanging things up for a few? [14:33] getting around 12-15secs now http://paste.ubuntu.com/25714094/ [14:43] bdx: ouch, looking [14:43] mhilton: ^ [14:44] so looking at that, 10s on the last line there getting the result form jimm? [14:46] totally [14:47] the 10s seems to be pretty consistent over many runs [14:50] bdx: yea, k. I'll see what we can find out. ty for the ping. [14:51] sweet, thanks [15:07] bdx: soooooo, good news and bad news [15:07] good news: mhilton knows exactly what's up and why I don't see it... [15:08] bad news: in order to show machine/unit counts in your model list jimm will juju status each model to get those values and that's gotten slow and ungood with your models as you get more [15:15] oh darnnn [15:15] lol [15:15] well, thanks for digging into that [15:15] good to know I guess [15:16] rick_h: I've got a few questions about CMR, I'll bring them up in #juju-dev [15:17] bdx: just do #juju