make magic-folder (downloader) polling interval configurable #2829
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#2829
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
It's not currently possible to configure the polling interval for the magic-folder downloader.
Additionally, we should think about what a good default is (3 seconds was used during development, but that's way too short).
We also should document this behavior and say something about how to choose a default (e.g. maybe a rough estimate of how much traffic it means).
For a first cut, at least making "a" config-option is a must for 0.1.12
Longer term, it might be good to have other ways of scheduling magic-folder syncs. (e.g. even "only when told to" or schedule times of low-freq/high-freq, etc).
I checked and currently MagicFolder defaults to a 1 second polling interval.
Here's I've changed it to 5 seconds default and made it configureable via a magic folder polling interval config file option:
https://github.com/david415/tahoe-lafs/tree/2829.magic_folder_polling_interval.0
https://github.com/david415/tahoe-lafs/commit/63e52c276ba3d2e13dd55b74d2c88e4456b168f4
upon looking at the code more closely i don't understand why we have two delay variables in the queue mixin:
the scan interval only controls how often when_queue_is_empty is called which is only used by the Downloader which performs a remote collective dir scan every scan interval. having the scan interval and the turn delay be different for the Downloader does nothing special.
the uploader doesn't even use when_queue_is_empty. it's a no-op.
can we get rid of scan_interval?
I certainly do not like shadowing variable in mixins and in the inheriting class.
i added more commits to that dev branch experimenting with removing scan_interval. it did not work out so well. the unit tests... many of them fail. not sure why.
See https://github.com/tahoe-lafs/tahoe-lafs/pull/371
Landed in [233d0e2].
Closed as fixed since the PR was merged.