These are chat archives for ManageIQ/manageiq/performance

9th
Nov 2016
Halász Dávid
@skateman
Nov 09 2016 08:56
guys, i see a lot of DB checkins/checkouts in the development log when serving assets :(
Joe Rafaniello
@jrafanie
Nov 09 2016 12:38
That's rails. The query cache Middleware still calls connection in order to know the cache parameters
Thankfully, in production, apache serves them
Keenan Brock
@kbrock
Nov 09 2016 15:14
I was trying to avoid those. thanks for info @jrafanie
@skateman do you run nginx (or apache) locally? or just rails s?
Halász Dávid
@skateman
Nov 09 2016 15:15
@kbrock just rails s
I'm a UI dev
Keenan Brock
@kbrock
Nov 09 2016 15:16
on other projects every dev ran the production web server locally
there were redirects and stuff
which makes sense
run in as close as production as possible
Halász Dávid
@skateman
Nov 09 2016 15:16
yes, but if you're working with JS and CSS :) you can't really afford this
Keenan Brock
@kbrock
Nov 09 2016 15:17
b/c asset bundling and stuff?
well, soon enough, webpack may solve all our problems ;)
hmm. with less snark
when we go towards webpack, will that be a middleware that is different from our static asset serving?
Joe Rafaniello
@jrafanie
Nov 09 2016 20:04

That's rails. The query cache Middleware still calls connection in order to know the cache parameters

@skateman by the way, Matthew just pointed us to a PR that will fix that the db checkin/checkout problem on each rack request that hits the query_cache middleware: rails/rails#26978