How does tahoe filesystem layer (lafs) handle lots of file-upload tasks? #173
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
2 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#173
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?
Rob, Peter, Justin and I just fixed up the commercial, proprietary cousin of Tahoe -- the http://allmydata.com product -- to behave better when the user asks it to upload 100,000 files ASAP. How would Tahoe handle a similar situation? To close this ticket, implement an automated measurement (akin to the memory and upload/download rate measurements) which measures how much RAM, wall-clock time, CPU load, etc. a Tahoe node requires to simultaneously upload 1000, 10,000, or 100,000 files.
Fabrice, the entrepeneur behind Allmydata, says that our reference test should be 25,000 files and 100 GB -- "VERY WELL and RELIABLY!". He says this is necessary to be competitive with Carbonite, Mozy, etc.. He promises to raise the bar to 100,000 files and 500 GB as soon as we reach 25,000 files and 100 GB. ;-)
Putting this into the 0.9.0 (Allmydata 3.0 final) Milestone.
This ticket is just for the tahoe filesystem layer ("laughfs"). See also #337 (how does the whole system including the Windows native client handle lots of file-upload tasks?).
This ticket is hereby vagueified to be unclear about whether we're talking about lots of parallel upload tasks or a lot of sequential upload tasks or some combination thereof.
How does tahoe handle lots of simultaneous file-upload tasks?to How does tahoe filesystem layer (laughfs) handle lots of file-upload tasks?incidentally, I'm -1 on the "laughfs" term. I have no idea what it refers to.
How does tahoe filesystem layer (laughfs) handle lots of file-upload tasks?to How does tahoe filesystem layer (lafs) handle lots of file-upload tasks?