Source Server Specs

The code used to generate ResourceSync documents (rs_oaipmh_src.py) has only been tested on Linux; therefore, Linux is the recommended platform for running that code.

As far as server specs go:

• The amount of persistent storage required depends on the number of collections you have, and the number of items per collection (affects the size of ResourceLists), and the number of resources that are expected to be created/updated/deleted (affects the size of ChangeLists). Our test collection's ResourceList and ChangeList, each with 5,000 entries, both came out to 1.5 MB (so, 300 B per entry). So:

MIN_NUM_OF_BYTES =
  (
    (NUM_RESOURCES_COLLECTION_1 + NUM_ANTICIPATED_CHANGES_COLLECTION_1) +
    (NUM_RESOURCES_COLLECTION_2 + NUM_ANTICIPATED_CHANGES_COLLECTION_2) +
    ...
    (NUM_RESOURCES_COLLECTION_N + NUM_ANTICIPATED_CHANGES_COLLECTION_N)
  ) * 300 B

• The amount of memory required depends primarily on that required by your web server, but also on the requirements of the py-resourcesync library. No metrics have been made publicly available at this time, but we have tested the code on collections with up to resources, and have had no problems on a machine with GB.