These are chat archives for ManageIQ/manageiq/performance

1st
Apr 2019
Halász Dávid
@skateman
Apr 01 07:54
good morning
it is being used in a treebuilder for catalog entrypoint selection
the class is instantiated here and also for lazyload where it should somehow access the already cached data
I'm open for any better idea about where to store the cache, if we want API-like endpoints for our trees, the references to @sb should go from the TreeBuilders
@mkanoor says it's an expensive operation to build those data, so maybe it's worth it to save like this :confused:
I'd just rebuild this upon each request and store it in the tree instance
Halász Dávid
@skateman
Apr 01 08:03
maybe activerecord's cache is enough, the first request loading the tree and the lazyloading ones are kinda close to each other in time
skateman @skateman not knowing enough about activerecord caching :disappointed:
Halász Dávid
@skateman
Apr 01 14:22
@kbrock ? :wink:
or maybe @NickLaMuro ?
Keenan Brock
@kbrock
Apr 01 14:26
the sql has to be identical. event an extra limit 1 will mess it up
@skateman cache is only good in one request. not sure I understant "close to each other"
Halász Dávid
@skateman
Apr 01 14:28
oh, okay
so we have to store it in the session? :(
Keenan Brock
@kbrock
Apr 01 15:04
@skateman frustrating when something basically feels static takes a long time to load
# FIXME after euwe: build_ae_tree
lol
Halász Dávid
@skateman
Apr 01 15:05
working on it, I mean the fixme
Keenan Brock
@kbrock
Apr 01 15:05
would be nice to just d/TreeBuilder\.tree.*$/
Halász Dávid
@skateman
Apr 01 16:36
:D :D