>>
>> At this stage we could describe what we use for production equipment and
>> attempt to address any concerns you may have about your intended use
>>case.
>
>I would be really interested to hear about this.
>
>The specific item we are addressing in the document is: "Scalability --
>The purpose of this measure is to comment on the ability of a software
>to be able to handle a sufficiently large number of objects."
>
>I believe all that has been provided thus far, and the production
>examples should be sufficient for me to address this section. It sounds
>like given enough hardware, you can throw whatever you want at it within
>reason.
>
>-nruest
For an idea of objects in the system, our IQSS DVN currently has the
following: Dataverses: 494 | Studies: 51,637 | Files: 719,823
Dataverses are virtual repositories for individual researchers as well as
organizations. Studies can be either references to actual studies or
cataloging information metadata describing the work. Files of course are
individual data files and supporting documents.
Prior to migrating our infrastructure to the library this past October, we
were running our IQSS DVN on the following configuration:
2 web server instances with 2 quad core cpus and 48GB ram, running RHEL 5
(we're now running RHEL 6).
1 database server with 2 six core cpus running RHEL 5 and postgres 8.4 and
64GB memory
1 rserve server to do analytical analysis and format transformations with
2 six core cpus and 64GB memory
Load balanced by a Coyote Point Equalizer, model 450
This was a deluxe configuration intended to support whatever we threw at
it. Our new configuration is similar but running RHEL 6 and with bigger
machines due to the availability of newer equipment and the requirement to
support more, separate DVNs for the library.
To economize and plan for future scalability, we're looking at more
closely measuring actual usage and breaking out certain functions to
specific machines.