On Tue, Aug 03, 2010 at 09:44:53 +0200, Florian Gilcher wrote: > I think it would be interesting to have a binary that basically does all > the patch copying a get would do. I think it might be worthwhile to check > out the GHC dtrace probes first.
For what it's worth, I've been idly trying to cut darcs down to size at darcs get --lazy http://code.haskell.org/~kowey/cutdown-darcs Removed so far are things which aren't actually being used: - networking support - commands besides darcs get - support for external software - patch matching So these aren't code paths that are actually visited, we probably learn nothing new from tracing (it over darcs darcs), but I hope that over time we can pare this down even further, by removing patch application, as you point out. The end goal is to have a small demonstrator that captures the core performance problem and that we can show to folks outside the Darcs community for advice. Ripping out darcs subsystems is strangely fun. Gives you a feeling for how much intertwined or modular Darcs is. Join in! (set so that patches go to me) -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> For a faster response, please try +44 (0)1273 64 2905.
signature.asc
Description: Digital signature
_______________________________________________ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
