...
Advanced Tables - Table Plus | |||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||
|
If you have performance and scale expectations please provide details in whatever granularity makes sense regarding the composition and needs of your current or expected Fedora repository. You can edit this page and add your institution below.
...
migrating with probably around 100k objects (from Fedora 5.1.1), expected at 100 objects/minute.
Saxon State Library Dresden
- Repository size in number of objects and/or number of bytes
- ~500k objects
- ~30 million individual resources
- ~11 TB online
- ~1 PB off-site tapes
- Expected ingest rates
- metadata objects: ~1/s
- binaries: latency: <1s, speed: close to network bandwidth (non-blocking I/O)
- Expected access response times
- sub-second latency
- Migration scenarios: size and time expectations
- custom migration, ingesting new resources on masse; ~50k/day
- referencing a lot of externally stored content
- possibly parallel ingests
- Side loading
- I'd rather not use this and use the API at all times. Only if performance degrades to much.