Opened at 2008-03-10T19:51:16Z
Last modified at 2011-01-03T02:46:22Z
#337 new defect
how does the whole system handle lots of file-upload tasks?
| Reported by: | zooko | Owned by: | somebody |
|---|---|---|---|
| Priority: | major | Milestone: | eventually |
| Component: | code | Version: | 0.8.0 |
| Keywords: | scalability performance upload | Cc: | |
| Launchpad Bug: |
Description (last modified by davidsarah)
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. ;-)
This ticket is to implement automated measurements of the performance of the lots of file-upload tasks (with various levels of parallelism?), connecting to some relatively stable grid.
Change History (5)
comment:1 Changed at 2008-03-10T19:51:48Z by zooko
comment:2 Changed at 2008-03-10T19:54:59Z by zooko
- Summary changed from how does the Windows native client handle lots of file-upload tasks? to how does the whole system including the Windows native client handle lots of file-upload tasks?
comment:3 Changed at 2008-03-10T19:59:32Z by zooko
Note that we have to do this test manually before making a release of the allmydata.com backup product (and if we don't, Fabrice will). This ticket is about automating that process.
comment:4 Changed at 2009-12-13T06:00:34Z by davidsarah
- Keywords scalability performance windows upload added
comment:5 Changed at 2011-01-03T02:46:22Z by davidsarah
- Description modified (diff)
- Keywords windows removed
- Summary changed from how does the whole system including the Windows native client handle lots of file-upload tasks? to how does the whole system handle lots of file-upload tasks?
To what degree the Tahoe node sees the file-upload tasks as parallel or sequential is up to the Windows native client, and invisible to this automated test.