mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 17:16:00 +03:00
[GH-ISSUE #698] Feature Request: User defined backend timeout #439
Labels
No labels
expected: maybe someday
expected: next release
expected: release after next
expected: unlikely unless contributed
good first ticket
help wanted
pull-request
scope: all users
scope: windows users
size: easy
size: hard
size: medium
size: medium
status: backlog
status: blocked
status: done
status: idea-phase
status: needs followup
status: wip
status: wontfix
touches: API/CLI/Spec
touches: configuration
touches: data/schema/architecture
touches: dependencies/packaging
touches: docs
touches: js
touches: views/replayers/html/css
why: correctness
why: functionality
why: performance
why: security
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ArchiveBox#439
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @virtualadept on GitHub (Apr 9, 2021).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/698
Type
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 secondsDescribe 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?
@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.
@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) :)