[chef-dev] Re: [] Lightweight Search

[Adam Jacob < >]

Also, I've been playing around a bit with getting the size of the node 
objects saved to be smaller. The current leading contender is to whitelist 
the node attributes you actually want saved at the end of the run - this way 
all the attributes from Ohai + Cookbooks are available during the run, but 
only the ones you actually care about for search are saved. A working 
prototype is here:

https://github.com/opscode/whitelist-node-attrs

This should help in the near term - slim down the size of the objects to the 
parts you care about, and the aggregate size of the results will shrink as 
well. We should still fix the core issue of only returning full objects on 
search, but this should help in the interim.

-- 
Opscode, Inc.
Adam Jacob, Chief Product Officer
T: (206) 619-7151 E: 

 


On Wednesday, August 17, 2011 at 4:53 PM, Adam Jacob wrote:

> Hi Justin - this is high on our roadmap. 
> 
> Let's talk about what the high level interface will look like, and then we 
> can dig in to what a particular implementation would entail. Can you write 
> up what you are thinking about at Wikia?
> 
> -- 
> Opscode, Inc.
> Adam Jacob, Chief Product Officer
> T: (206) 619-7151 E: 
> 
 
>  
> (mailto:
 )
> 
> 
> On Wednesday, August 17, 2011 at 3:40 PM, Justin Alan Ryan wrote:
> 
> > Hello,
> > 
> > At a recent SV Chef meetup we discussed a problem we have at Wikia 
> > related to the memory requirements of our chef-client runs.
> > 
> > Many folks shared similar concerns and some folks from Opscode expressed 
> > that they are aware of the problem and that a solution may involve search 
> > calls specifying which attributes they need on returned nodes. 
> > 
> > I haven't heard of any movement on this, and we're considering writing a 
> > patch which implements an optional paramater for search and returns 
> > abbreviated JSON.
> > 
> > I talked to a couple of folks who suggested dropping a note here to see 
> > if we're potentially duplicating effort and/or if there is any such 
> > effort we can contribute to. 
> > 
> > I'll update as we make progress, thanks in advance for any input!
> > 
> > Justin
> > 
> > -- 
> > http://about.me/justizin