unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <ng0@libertad.pw>
To: 25045@debbugs.gnu.org
Subject: bug#25045: [Website] Packages page takes too long to load
Date: Fri, 02 Dec 2016 22:41:39 +0000	[thread overview]
Message-ID: <87k2bihs2k.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <87fumbmk8w.fsf@gnu.org>

Ludovic Courtès <ludo@gnu.org> writes:

> Luis Felipe López Acevedo <felipe.lopez@openmailbox.org> skribis:
>
>> On 2016-11-28 12:00, Alex Sassmannshausen wrote:
>>> Hi Luis,
>>>
>>> Indeed, I had a first bash at solving this problem by providing a
>>> set of
>>> static html pages paginated by the first letter of the package name.
>>>
>>> I'm not particularly wedded to this solution, so if you feel strongly
>>> about going another way, I'd be keen to hear/see about it.
>>>
>>> In the meantime, I'm open to testing/feedback.  I will unfortunately
>>> not
>>> be able to put work into this until at least Saturday/Sunday, as some
>>> Perl work has higher priority at the moment.
>>>
>>> But let me know if you have questions or feedback!
>>>
>>> Best wishes,
>>
>> Hi, Alex :)
>>
>> The solution I had in mind includes an alphabetic index, and
>> pagination as well. However, it includes a few more things, and would
>> take some time to design and implement. So I think we should use your
>> patch to fix the size issue as soon as possible.
>
> I agree!
>
> Alex, was there anything left to address?  If not, feel free to push.
> :-)
>
>> For what is worth, this is what I had in mind:
>>
>> /packages/
>> First page of the list of packages. Packages listed here only provide
>> a summary: package logo (if any), name, version, description, and an
>> indicator if it has issues. This page also has filters to find
>> packages (for now, alphabetic filter. In the future, category filter,
>> and search box).
>>
>> /packages/page/N/
>> Page N of the list of packages.
>>
>> /packages/a/
>> First page of the list of packages whose name starts with A. Packages
>> are presented the same way as in /packages/.
>>
>> /packages/a/page/N/
>> Page N of the list of packages starting with letter A.
>>
>> /packages/icecat/X.Y.Z/
>> Page with details about IceCat version X.Y.Z. It includes all the
>> information about this package, including its issues (which are
>> currently listed in a separate page along with the issues of other
>> packages: /packages/issues.html). Including the issues of a package in
>> its detail page could avoid having the current issues page grow too
>> much, like the current Packages page.
>>
>> This static pagination and filtering would generate A LOT of pages,
>> but of reasonable size for web browsers to load.
>
> Sounds like a good plan as well, though that’s indeed a lot of web pages
> for that rusty CVS repo to handle…

If I remember correctly, Gnu projects do not have to host their
websites on gnu.org, if the CVS should be the blocker to move
forwards and stay static.
But with every package and every version of them we add, this
would add a lot of generated pages (right now around 4550
packages and rising), so it might get difficult to manage that
unless management for this in place somehow (gets cleared on
reboot, make clean, or something similar).

> Medium-term, I think we should consider a solution involving pages
> generated on the fly server-side, with a caching proxy (nginx!) in front
> of it.  We’ll have to seek assistance from the gnu.org web masters, but
> ISTR they were not against that idea.
>
> Thanks!
>
> Ludo’.
>
>
>
>

-- 
♥Ⓐ  ng0  | ng0.chaosnet.org

      parent reply	other threads:[~2016-12-02 22:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-27 19:19 bug#25045: [Website] Packages page takes too long to load Luis Felipe López Acevedo
2016-11-27 23:10 ` Ludovic Courtès
2016-11-28 17:00   ` Alex Sassmannshausen
2016-11-28 18:41     ` Luis Felipe López Acevedo
2016-11-28 20:18       ` Ludovic Courtès
2016-11-29  9:12         ` Alex Sassmannshausen
2016-12-09 22:40           ` Ludovic Courtès
2016-12-02 22:41         ` ng0 [this message]

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k2bihs2k.fsf@we.make.ritual.n0.is \
    --to=ng0@libertad.pw \
    --cc=25045@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).