optimization of propfind

[tolsen]

propfind_one should be O(1) in number of queries. propfind should be O(depth of tree).

read catacomb paper. take care of binds.

[tolsen]

question from Ritesh

To find property value of a resource, a seperate query to the database is issued for each resource association (locks, acl, parents, body -> in case of allprop). These queries are send for each node in the tree.

Will 'eager loading of associations' be a better option? This definitely would result into reduction of no. of queries, but am not sure this would improve performance as database still needs to send data. Also, when only some properties are requested for, it might be possible that we are asking for more data then required.

[tolsen]

comment from Nakul:

You can look at 'piggy backing' (  http://railsexpress.de/blog/articles/2006/05/29/simpler-piggy-backing) an alternate optimized way of eager loading.

Thanks, Nakul