That definitely improved the performance. The time it takes to run went from 6+ minutes to 1m7s. It's pretty much the same speed as the individual queries now. The performance is still significantly worse than 1.6.17 was and I don't know if that should be addressed.
-----Original Message----- From: Philip Martin [mailto:[email protected]] Sent: Friday, September 02, 2011 4:38 AM To: RYTTING,MICHAEL (A-ColSprings,ex1) Cc: [email protected]; [email protected] Subject: Re: [PATCH] Improve speed of recursive info Philip Martin <[email protected]> writes: > Philip Martin <[email protected]> writes: > >> So that indicates that we >> have a scaling problem, and I suspect the ORDER/GROUP part of >> STMT_SELECT_NODE_CHILDREN_WALKER_INFO. I don't know whether that is >> enough to explain the extreme runtime you are getting. > > Michael, are you building 1.7 from source? Will you try a patch? The > following patch against 1.7 addresses the above problem and improves > the speed of recursive info on my machine: It looks like we might be able to fix this using another SQL index rather than changing the C code. You can create the index in an existing working copy using: sqlite3 .svn/wc.db "create index i_p2 on nodes(wc_id, parent_relpath, local_relpath, op_depth)" -- uberSVN: Apache Subversion Made Easy http://www.uberSVN.com
