From: Baptiste Daroussin <bapt@FreeBSD.org>
To: tech@mdocml.bsd.lv
Subject: New db format (was Re: call for testing: mandoc-1.13.4 release candidate)
Date: Sat, 9 Jul 2016 17:29:27 +0200 [thread overview]
Message-ID: <20160709152926.42bre6tittzmpm2g@ivaldir.etoilebsd.net> (raw)
In-Reply-To: <97865.1468074718@CATHET.us>
[-- Attachment #1: Type: text/plain, Size: 1851 bytes --]
On Sat, Jul 09, 2016 at 08:31:58AM -0600, Anthony J. Bentley wrote:
> Baptiste Daroussin FreeBSD writes:
> > > P.S.
> > > It seems likely that this will be the last release needing SQLite
> > > for database support. I have started work on removing the dependency
> > > on SQLite without loss of functionality and without needing any
> > > replacement, relying on POSIX interfaces only. So it is likely
> > > that we will have a 1.14.1 release this autumn that no longer needs
> > > SQLite.
> >
> > Tell me more, I'm really interestedin that, is there a place were we can
> > look at this work in progress code?
>
> Ingo sent an initial patch to the OpenBSD tech@ list a few days ago:
>
> https://marc.info/?l=openbsd-tech&m=146734380814620&w=2
>
Thank you,
Beside minor portability issues (that I will provide fixes for once this patch
is official) I can say it works fine on FreeBSD :)
Tested on FreeBSD 12-CURRENT:
The 3 main "bad" feedbacks I got about mandoc was:
- time to create the db was long with sqlite with the new code it is longer:
does from 4s to 11s in general for the base manpages but I do not consider
that as a big issue given it is not run that often and the code is quite new
and there are probably room of improvements
- size of the db (for embedded). With the new code:
3.8M /usr/share/man/mandoc.db
1.6M /usr/share/man/mandoc.new.db
This is a big improvement
- apropos can be very slow before showing anything, with the new code, it is
instant!
old 'apropos ls':
8.67 real 3.63 user 5.03 sys
new 'apropos ls':
0.02 real 0.02 user 0.00 sys
I notice some memory corruption in the ouput of apropos, I haven't dig into it
yet
Great work, I'm eager to see that code in!
Best regards,
Bapt
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-07-09 15:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <sfid-H20160709-151232-+015.17-1@spamfilter.osbf.lua>
[not found] ` <20160709131158.GA6629@athene.usta.de>
2016-07-09 13:18 ` call for testing: mandoc-1.13.4 release candidate Thomas Klausner
2016-07-09 15:30 ` Ingo Schwarze
2016-07-09 13:39 ` Baptiste Daroussin FreeBSD
2016-07-09 14:31 ` Anthony J. Bentley
2016-07-09 15:29 ` Baptiste Daroussin [this message]
2016-07-09 16:12 ` New db format Ingo Schwarze
2016-08-05 20:26 ` Baptiste Daroussin
2016-07-09 14:28 ` call for testing: mandoc-1.13.4 release candidate Svyatoslav Mishyn Crux
2016-07-10 14:08 ` Ingo Schwarze
2016-07-09 18:21 ` Svyatoslav Mishyn
2016-07-09 21:13 ` Ingo Schwarze
2016-07-09 18:55 ` Svyatoslav Mishyn Crux
2016-07-10 10:46 ` Svyatoslav Mishyn
2016-07-10 13:39 ` Ingo Schwarze
2016-07-10 14:27 ` Christian Neukirchen
2016-07-10 16:36 ` Ingo Schwarze
2016-07-10 16:48 ` Christian Neukirchen
2016-07-10 18:34 ` Ingo Schwarze
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160709152926.42bre6tittzmpm2g@ivaldir.etoilebsd.net \
--to=bapt@freebsd.org \
--cc=tech@mdocml.bsd.lv \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).