On the "lower end of things" (somewhat to Robin's point): Until a few week's back here were the stats for http://demo.dspace.org virtual server: * Amazon EC2 "m1.small" virtual server * 1 vCPU * 1.7GB of RAM * Ran JSPUI, XMLUI, OAI, LNI, SWORD (v1 and v2) simultaneously * Tomcat, Postgres & DSpace all on the same virtual server
It was only upgraded when we began to finally hit up against the limited memory as we began to add even more apps (REST API & similar). Currently, http://demo.dspace.org is: * Amazon EC2 "m1.medium" virtual server * 1 vCPU * 3.75GB of RAM * Again, everything still runs on the same virtual server. For DSpaceDirect (http://www.dspacedirect.org), we have a similar setup. Since all of our initial customer sites are small (few thousand items or less), we can get by with only 2GB of memory per customer site. We also run everything (Postgres, Tomcat, etc) on one instance, at least at this time. So, it definitely depends on how you are using DSpace and how much content is actually in your DSpace. More content tends to translate into more site activity and therefore a need for more memory (or for splitting database and application on separate servers, or similar). I think the minimum recommended setup is much more simplistic than the high-activity, high-performance DSpace sites out there. Smaller sites really should be able to run everything on one server, and likely only need around 2-4GB of memory to start with (again depending on number of items & amount of anticipated activity). So a "bare minimum" production setup is likely along the lines of: 1 CPU, 2GB of RAM. - Tim On 11/19/2013 3:16 AM, TAYLOR Robin wrote: > Hi Hardy, > > I am a little wary about recommending hardware, there are so many > different use cases for DSpace out there. I was once contacted by an > architects office that just wanted somewhere to store their drawings. The > danger is that someone considering DSpace may conclude that our > recommendation is the minimum requirement, when their use case would > require something more lightweight. In some cases a PC in the corner of > the room with some backup facility might be sufficient. > > Cheers, Robin. > > > On 18/11/2013 20:24, "Pottinger, Hardy J." <pottinge...@missouri.edu> > wrote: > >> Hi, I have been asking around privately for hardware recommendations for >> running DSpace in production, and I noticed we have an old page of advice >> here: >> >> https://wiki.duraspace.org/display/DSPACE/EndUserFaq >> >> >> We should probably have a page of hardware advice for production DSpace on >> the "official" DSpace wiki (that End User FAQ page isn't quite there). >> >From all my asking around, here's what I've come up with for production: >> >> First, there's a question of approach. Most of the people I asked were >> running PostgreSQL on a separate machine (DB tuning and troubleshooting is >> not the same thing as Tomcat tuning and troubleshooting). >> >> So, if one is running an application stack on one machine, and a DB on >> another machine, the specs for those machines would be different than an >> "everything on one box" approach. Everything on one box is appropriate for >> a staging/development server (which would have smaller requirements than >> production). I've got a pretty good idea of what to recommend for the >> application stack box and DB box, so I'll include those specs below. But, >> if you have another suggestion, I'd love to hear about it. >> >> Three-box approach to DSpace >> >> Production Application Box: >> 4 CPU, 4GB of RAM, and with the following stack set up (note some of this >> is specific to our environment): >> Java 7 (OpenJDK is fine) >> Tomcat 7 >> Ant 1.8.2 or higher >> Maven3 (3.0.4 or higher) >> Shibboleth SP 2.5 or higher (optional) >> Apache 2.0 (optional) >> PHP 5.3.3 (optional) >> As much storage as you need for your production bitstream content (very >> environment-specific, external SAN storage recommended) >> >> Production DB Box: >> 1 CPU, 2GB of RAM >> With this software installed: >> PostgreSQL server >> >> As much storage as you need for a DB, probably the default space for your >> VM will be sufficient. >> >> >> Staging Box (everything on one box): >> 2 CPU, 2GB of RAM, and with the following stack set up (note some of this >> is specific to our environment): >> Java 7 (OpenJDK is fine) >> Tomcat 7 >> Ant 1.8.2 or higher >> Maven3 (3.0.4 or higher) >> Shibboleth SP 2.5 or higher (optional) >> Apache 2.0 (optional) >> PHP 5.3.3 (optional) >> PostgreSQL server >> >> As much storage as you need for your staging and development bitstream >> content (very environment-specific, external SAN storage recommended) >> >> >> >> -- >> HARDY POTTINGER <pottinge...@umsystem.edu> >> University of Missouri Library Systems >> http://lso.umsystem.edu/~pottingerhj/ >> https://MOspace.umsystem.edu/ >> "We shall not cease from exploration, and at the end of all our exploring >> will be to arrive where we started and know the place for the first time." >> --T.S. Eliot >> >> >> >> >> -------------------------------------------------------------------------- >> ---- >> Shape the Mobile Experience: Free Subscription >> Software experts and developers: Be at the forefront of tech innovation. >> Intel(R) Software Adrenaline delivers strategic insight and game-changing >> conversations that shape the rapidly evolving mobile landscape. Sign up >> now. >> http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktr >> k >> _______________________________________________ >> Dspace-devel mailing list >> Dspace-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/dspace-devel > > ------------------------------------------------------------------------------ Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk _______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
