From: tornaria <tornaria@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Update pari optional packages
Date: Tue, 24 Aug 2021 23:13:15 +0200 [thread overview]
Message-ID: <20210824211315.xgVaXB3ZxY41DFYYYuBPXPwy8BcNExVhvva6fYZxBiA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32641@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1673 bytes --]
New comment by tornaria on void-packages repository
https://github.com/void-linux/void-packages/pull/32641#issuecomment-904980981
Comment:
> I'm also considering adding packages `pari-elldata-small` and `pari-galpol-small` with small versions of the databases that should be good for testing and small computations.
RFC on `*-small` packages: is it worth it?
What I propose is that for the larger databases (elldata, galpol, seadata) we have a small subset that is good for moderate sizes, and enough for testing. As an example:
- pari-elldata: full database for conductors up to 500k is 57M installed size. A reasonable small subset is conductors up to 20k which would take 1.8M of installed size.
- pari-galpol: full database for group orders up to 143 is 73M installed size. The subset for orders up to 64 would take 12M installed size.
- pari-seadata: normal database for primes up to 750 bits is 19M. The small database for primes up to 350 bits would be 668K. In this case there's also a "-big" version for primes up to 1100 bits which takes about 120M installed size.
The `pari-seadata-small` is suggested by upstream and it's already in this PR. The other two are easy to do.
The complete installation of pari with small databases would shrink from ~175M to ~40M of installed size (right now this is ~300M, we already save ~125M just by installing gzipped files which pari reads fine).
All databases would be incremental, e.g. `pari-elldata-small` installs small subset, `pari-elldata` contains the rest and depends on `pari-elldata-small`, etc. so this makes no difference for existing installations.
@motorto @dkwo: what do you think?
next prev parent reply other threads:[~2021-08-24 21:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 2:13 [PR PATCH] " tornaria
2021-08-23 23:03 ` [PR PATCH] [Updated] " tornaria
2021-08-23 23:04 ` tornaria
2021-08-24 21:13 ` tornaria [this message]
2021-08-25 7:41 ` dkwo
2021-08-25 7:43 ` dkwo
2021-08-26 15:58 ` [PR PATCH] [Updated] " tornaria
2021-08-26 16:00 ` tornaria
2021-09-04 14:55 ` motorto
2021-09-04 16:08 ` tornaria
2021-09-04 17:33 ` motorto
2021-09-04 19:14 ` [PR PATCH] [Updated] " tornaria
2021-09-04 19:24 ` tornaria
2021-09-06 9:32 ` dkwo
2021-10-27 2:09 ` [PR PATCH] [Updated] " tornaria
2021-10-27 2:12 ` tornaria
2021-10-30 20:10 ` tornaria
2021-10-30 20:17 ` ericonr
2021-11-09 16:00 ` [PR PATCH] [Merged]: " leahneukirchen
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=20210824211315.xgVaXB3ZxY41DFYYYuBPXPwy8BcNExVhvva6fYZxBiA@z \
--to=tornaria@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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).