[GH-ISSUE #698] Feature Request: User defined backend timeout #439

Closed
opened 2026-03-01 14:43:37 +03:00 by kerem · 2 comments
Owner

Originally created by @virtualadept on GitHub (Apr 9, 2021).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/698

Type

  • Request modification of existing behavior or design

What is the problem that your feature request solves

When doing a huge search query (like to batch add tags) the following error is thrown

Error from the search backend, only showing results from default admin search fields - Error: Command '['rg', '--type-add', 'ignore:*.{css,js,orig,svg}', '-ilTignore', '-e', 'BIGSEARCHSTRING', '/data/archive']' timed out after 60 seconds

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

A config option to increase the timeout from 60 seconds to a user defined amount.

How badly do you want this new feature?

  • It would be nice to have eventually
Originally created by @virtualadept on GitHub (Apr 9, 2021). Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/698 <!-- Please fill out the following information, feel free to delete sections if they're not applicable or if long issue templates annoy you :) --> ## Type - [X] Request modification of existing behavior or design ## What is the problem that your feature request solves When doing a huge search query (like to batch add tags) the following error is thrown `Error from the search backend, only showing results from default admin search fields - Error: Command '['rg', '--type-add', 'ignore:*.{css,js,orig,svg}', '-ilTignore', '-e', 'BIGSEARCHSTRING', '/data/archive']' timed out after 60 seconds` ## Describe the ideal specific solution you'd want, and whether it fits into any broader scope of changes A config option to increase the timeout from 60 seconds to a user defined amount. ## How badly do you want this new feature? - [X] It would be nice to have eventually
Author
Owner

@pirate commented on GitHub (Apr 9, 2021):

Good idea, done: 3276434. Will be out with v0.6. I also upped the default to 90sec.

Out of curiosity how large is your archive? And are you using an SSD or HDD? We have no analytics, so the only way I get feedback from users on speed is by hearing about it in issues.

<!-- gh-comment-id:816392394 --> @pirate commented on GitHub (Apr 9, 2021): Good idea, done: 3276434. Will be out with v0.6. I also upped the default to 90sec. Out of curiosity how large is your archive? And are you using an SSD or HDD? We have no analytics, so the only way I get feedback from users on speed is by hearing about it in issues.
Author
Owner

@virtualadept commented on GitHub (Apr 9, 2021):

Current size of my archive is 3684 items. My sqlite db is about 49 megs. Its writing to a xcp-ng vhd on a 4 drive zfs pool with not-very-fast HDDs Since I have all of my VM's on that pool, it has to compete with writes, so that has to be considered.

However, until a recent update, rendering the main page was super-super slow, like almost browser-timeout levels of slow.
Since the latest release the web interface has been really snappy and responsive. It was a pretty shocking change (like I thought something was broken on the backend after the update).

Tagging 1k+ item, with exception of the db timeout, with everything considered was pretty fast.

If you want any more data let me know. I can also run benchmarking software if you write it for me (I'm not a coder) :)

<!-- gh-comment-id:816806740 --> @virtualadept commented on GitHub (Apr 9, 2021): Current size of my archive is 3684 items. My sqlite db is about 49 megs. Its writing to a xcp-ng vhd on a 4 drive zfs pool with not-very-fast HDDs Since I have all of my VM's on that pool, it has to compete with writes, so that has to be considered. However, until a recent update, rendering the main page was super-super slow, like almost browser-timeout levels of slow. Since the latest release the web interface has been really snappy and responsive. It was a pretty shocking change (like I thought something was broken on the backend after the update). Tagging 1k+ item, with exception of the db timeout, with everything considered was pretty fast. If you want any more data let me know. I can also run benchmarking software if you write it for me (I'm not a coder) :)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ArchiveBox#439
No description provided.