[GH-ISSUE #312] Server side pagination #229

New issue

Closed

opened 2026-03-01 14:41:41 +03:00 by kerem · 2 comments

kerem commented

2026-03-01 14:41:41 +03:00

Owner

Originally created by @eSoares on GitHub (Jan 21, 2020).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/312

Type

General question or discussion
Propose a brand new feature
Request modification of existing behavior or design

What is the problem that your feature request solves

Currently no pagination is performed in the server side. Yes, jQuery Datatables is used and can provide pagination, but if you amount of links grows it will terribly slow at the opening the page, not solving the problem at all since the problem is the browser render.
The problem are browsers are not designed to handle HTML tree so big.

In my current setup I have archived above 10k urls, which make ArchiveBox almost impossible to open. The index.html file returned from the server is 57MB.

Describe the ideal specific solution you'd want, and whether it fits into any broader scope of changes

The best solution would be supporting pagination from server side, and perform AJAX requests on the web page to load more results.

Extra note: with the pagination, search on the server also needs to be supported.

How badly do you want this new feature?

It's an urgent deal-breaker, I can't live without it

Currently is a deal breaker for me to use part of the project, since is impossible to even load the start page.

Originally created by @eSoares on GitHub (Jan 21, 2020). Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/312 ## Type - [ ] General question or discussion - [ ] Propose a brand new feature - [x] Request modification of existing behavior or design ## What is the problem that your feature request solves Currently no pagination is performed in the server side. Yes, jQuery Datatables is used and can provide pagination, but if you amount of links grows it will terribly slow at the opening the page, not solving the problem at all since the problem is the browser render. The problem are browsers are not designed to handle HTML tree so big. In my current setup I have archived above 10k urls, which make ArchiveBox almost impossible to open. The index.html file returned from the server is 57MB. ## Describe the ideal specific solution you'd want, and whether it fits into any broader scope of changes The best solution would be supporting pagination from server side, and perform AJAX requests on the web page to load more results. Extra note: with the pagination, search on the server also needs to be supported. ## How badly do you want this new feature? - [x] It's an urgent deal-breaker, I can't live without it Currently is a deal breaker for me to use part of the project, since is impossible to even load the start page.

kerem

2026-03-01 14:41:41 +03:00

closed this issue
added the
why: functionality

touches: data/schema/architecture

size: medium
labels

kerem commented

2026-03-01 14:41:42 +03:00

Author

Owner

@pirate commented on GitHub (Feb 4, 2020):

This is fixed in v5.0 with archivebox server (it's a full Django server with server-side search in v5 and server-side pagination). Follow this PR for future progress https://github.com/pirate/ArchiveBox/pull/275

@pirate commented on GitHub (Feb 4, 2020): This is fixed in v5.0 with `archivebox server` (it's a full Django server with server-side search in v5 and server-side pagination). Follow this PR for future progress https://github.com/pirate/ArchiveBox/pull/275

kerem commented

2026-03-01 14:41:42 +03:00

Author

Owner

@pirate commented on GitHub (Jul 24, 2020):

This is released in the new 0.4 branch.

@pirate commented on GitHub (Jul 24, 2020): This is released in the new 0.4 branch.

kerem referenced this issue

2026-03-01 14:48:26 +03:00

[PR #229] [MERGED] only use stdin if it has a value #1102

kerem referenced this issue

2026-03-01 18:00:08 +03:00