Versions Compared

Old Version 1

changes.mady.by.user David Wilcox

Saved on

compared with

New Version Current

changes.mady.by.user Ralf Claussnitzer

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Advanced Tables - Table Plus
columnStyles
autoNumbertrue


InstitutionRepository SizeNumber of ObjectsIngest RateAccess Response
Columbia University10 PB (external)25 millionNo worse than Fedora 3No requirements
National Library of Medicine70 TB20 million10K objects / hourNo requirements
UNC Chapel Hill200 TB10 million< 50ms / RDF ContainerSimilar to Fedora 4/5
Berlin State Library2 PB100 million (multiple Fedoras)10K objects / hourNo requirements
Zuse Institute Berlin100 TB20 million6K objects / hour20ms / object

Saxon State Library Dresden

1 PB30 million~1 object / ssub-second latency



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

  1. Repository size in number of objects and/or number of bytes
    1. ~500k objects
    2. ~30 million individual resources
    3. ~11 TB online
    4. ~1 PB off-site tapes
  2. Expected ingest rates
    1. metadata objects: ~1/s
    2. binaries: latency: <1s, speed: close to network bandwidth (non-blocking I/O)
  3. Expected access response times
    1. sub-second latency
  4. Migration scenarios: size and time expectations
    1. custom migration, ingesting new resources on masse; ~50k/day
    2. referencing a lot of externally stored content
    3. possibly parallel ingests
  5. Side loading
    1. I'd rather not use this and use the API at all times. Only if performance degrades to much.