Date: Sun, 13 May 2007 22:00:46 +0100 From: "Thomas Sparrevohn" <Thomas.Sparrevohn@btinternet.com> To: "'Kris Kennaway'" <kris@obsecurity.org> Cc: 'Benjamin Lutz' <mail@maxlor.com>, freebsd-hackers@freebsd.org, 'Michel Talon' <talon@lpthe.jussieu.fr> Subject: RE: DPS Initial Ideas Message-ID: <004301c795a1$c7e89410$57b9bc30$@Sparrevohn@btinternet.com> In-Reply-To: <20070513202737.GA63102@xor.obsecurity.org> References: <20070512004209.GA12218@lpthe.jussieu.fr> <20070513103757.GA33322@turion.vk2pj.dyndns.org> <200705131258.50309.Thomas.Sparrevohn@btinternet.com> <200705132042.26167.mail@maxlor.com> <001701c7959c$5ab84110$1028c330$@Sparrevohn@btinternet.com> <20070513202737.GA63102@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> FYI, "Using XML" and other buzzword-compliance is not currently on the > table either. Let's all try to maintain some focus, OK? > Well - I now heard the SQL buzzword quite a bit ;-) - but whatever - No matter what angle I take on the register/make INDEX timing issues they are insignificant compared to potential gains in the "single vs. Parallel" builds scenario - even with my UP system - a total rebuild of the ports I had installed took way > 24 hours of which the time used in "register" etc was and are only a fraction In my view ports should be self contained within the FreeBSD system - Focusing on The on-disk format seems to be the wrong angle on the issue - The current structure Works well - but it has a number of drawbacks - however it no way clear whether that The answer is another INDEX/storage structure
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?004301c795a1$c7e89410$57b9bc30$>