mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 17:16:00 +03:00
[GH-ISSUE #994] Feature Request: Limits for parallel processes of chrome #619
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#619
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 @juev on GitHub (Jun 28, 2022).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/994
Type
What is the problem that your feature request solves
In this time Archive box will run many chrome processes. How many processes we don't know. We have situation, when chrome processes eats all system resources.
Some backgrounds:
Describe the ideal specific solution you'd want, and whether it fits into any broader scope of changes
We have separate options, which limits how many links will processed in parallel. It will limit number of running chrome processes.
What hacks or alternative solutions have you tried to solve the problem?
Just restart docker compose. :(
How badly do you want this new feature?
@pirate commented on GitHub (Jan 19, 2024):
Going to close this as stale for now since I haven't seen this happen in a while.
Let me know if you're still seeing this issue in version >=
0.7.2or:dev. Chrome headless is much improved since the time this ticket was open.