These are chat archives for ManageIQ/manageiq/performance

3rd
Nov 2016
Daniel Berger
@djberg96
Nov 03 2016 17:15
@kbrock recommendations for optimizing an IN clause?
Keenan Brock
@kbrock
Nov 03 2016 17:15
@djberg96 more context
best would be to keep the in clause as a select
Daniel Berger
@djberg96
Nov 03 2016 17:15
orchestration stacks for azure
Keenan Brock
@kbrock
Nov 03 2016 17:15
not do a pluck or map
heh
@djberg96 do you have a rough draft "ugly" ruby version of your query?
aka - I'm not going to judge
Nick LaMuro
@NickLaMuro
Nov 03 2016 17:17
@djberg96 If you are trying to avoid a bomb of IDs in the IN clause, then it is best to switch that to a JOIN if possible (assuming I am understanding things correctly)
Daniel Berger
@djberg96
Nov 03 2016 17:17
well, originally we had a bunch of individual selects
Nick LaMuro
@NickLaMuro
Nov 03 2016 17:17
Nested select is another, but it really isn't solving the issue, just changing what generates the IDs (ruby v.s. the DB)
Keenan Brock
@kbrock
Nov 03 2016 17:17
IN is nice that it avoids the distinct but
Daniel Berger
@djberg96
Nov 03 2016 17:17
which was slow, so it was altered to use a single big IN clause
though it's old
@NickLaMuro probably easiest thing to do would be to have you add an azure cloud provider to a local instance
then let you watch the sql on the console during a refresh
Nick LaMuro
@NickLaMuro
Nov 03 2016 17:22
There an easy "step by step" I could do to do that?
Daniel Berger
@djberg96
Nov 03 2016 17:23
I'll send you some credentials
Chris Arcand
@chrisarcand
Nov 03 2016 17:23
@djberg96 He needs azure account access and all that though, no?
Daniel Berger
@djberg96
Nov 03 2016 17:23
@chrisarcand yeah, i'll setup a service principal for him
Joe Rafaniello
@jrafanie
Nov 03 2016 19:02
Interesting thread on puma and memory growth. https://github.com/puma/puma/issues/1047#issuecomment-257904428 Don't tell @chessbyte. :wink:
Oleg Barenboim
@chessbyte
Nov 03 2016 19:17
@gtanzillo @jrafanie @Fryguy can we move back to Thin?? I STILL do not understand what we are gaining with Puma
I see the problems, issues, bugs, etc -- just no benefit
Jason Frey
@Fryguy
Nov 03 2016 19:18
now that we are on ActionCable for notifications, I'm not sure we can go back
but I could be wrong
Daniel Berger
@djberg96
Nov 03 2016 19:18
i_know_some_of_these_words.jpg
@jrafanie j/k, I do sorta follow it, but I've never really dug into the memory management aspect of Ruby
Chris Arcand
@chrisarcand
Nov 03 2016 19:24
@Fryguy Nope, should be ok with thin there.
Daniel Berger
@djberg96
Nov 03 2016 19:31
@chrisarcand puma works with JRuby, while Thin does not, correct?
(not that I'm saying that should be a deciding factor)
Chris Arcand
@chrisarcand
Nov 03 2016 19:33
Oh bummer. I’d really like to see us heading towards JRubybility; might be some big benefits someday. Truffle just looks way, way too nice.