The hardware you will need to establish an NSDL EduPak educational resources repository will vary depending on overall requirements. For example, decisions regarding how many objects and in what types of formats your repository will house, and what services your repository will provide impact hardware choices.
A basic hardware scenario might look like this for a use case for 1K repository resources with all EduPak applications installed:
•512 MB RAM and at least 500 MB of available disk space should be available for the evaluation application
•Testing is recommended for production deployment. Content types such as videos or music make a big difference in how much disk space is required
A note on estimating disk space: Based on the NSDL data, we’re seeing about .016 MB disk space per record. That includes all filesystem and database storage. With NCS and DDS in the picture, an increase of 50-100% to .024 - .032 could be expected.
Current installed versions of NSDL EduPak 1.0 on Linux VM Tomcat use about 290 MB of memory, based on before and after startup math. The java process itself is using 267 MB resident, 507 MB virtual memory. PostgreSQL is 7 and 100 MB, respectively.






Leave a Comment
* You can follow any responses to this entry through the RSS 2.0 feed.