DPS Initial Ideas
Benjamin Lutz
mail at maxlor.com
Sun May 13 21:55:19 UTC 2007
On Sunday 13 May 2007 23:00, Thomas Sparrevohn wrote:
> 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
When coming up with ideas what to change INDEX's storage method to, just
keep in mind that
- There is very little flexibility whatsoever in the way data is stored
in the file. Each entry in the INDEX has its 13 or so fields, and
that's it. One of the strengths of XML, self-descriptiveness for very
dynamic data structures, doesn't matter for INDEX. Basically, imho,
using XML for tabular data = bad.
- INDEX exists for speed. Accessing the information in it should be as
fast as possible. I object to any change that increases the time
needed to search for and parse INDEX entries. I've written a little
searching tool (it can be found ports-mgmt/psearch). If INDEX were to
be converted to XML, just because of that it would be considerably
slower. If psearch then were to use standard XML parsing libs, the
slowdown would probably be at least an order of magnitude.
If there's any change to INDEX's format, it should make access faster,
not slower. A format that allows constant-time random access would be
nice, for example.
- INDEX does not need to be portable. It'll be used on FreeBSD systems
only, and by tools written specifically for the ports system.
The second point is most important here. This whole thread exists
because people consider the existing ports system to be too slow. How
is using XML going to help with that at all?
Cheers
Benjamin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20070513/7df351c4/attachment.pgp
More information about the freebsd-hackers
mailing list