I'd like to point out that the discussion is broadening considerably: a system can be slow for many reasons, not just memory starvation.
Step 1: what resource(s) are you short of? Something like LambdaProbe can peek inside Tomcat and show you how much of each of the various memory pools is being used. OS tools can show whether you are swapping heavily or spending a lot of time in I/O wait or are really CPU-bound (and what, besides Tomcat, may be eating CPU). DBMS tools can reveal places in the schema that don't scale well, queries that could be optimized, and additional indices that would be beneficial. It would be really helpful for large, busy sites with performance problems to share any such detailed observations. Some of those problems can probably be tuned away, and some will point to specific things for coders to investigate. Scaling experience will be valuable both in documenting good ways to tune up for DSpace and in finding design hotspots for rework. -- Mark H. Wood, Lead System Programmer [email protected] Balance your desire for bells and whistles with the reality that only a little more than 2 percent of world population has broadband. -- Ledford and Tyler, _Google Analytics 2.0_
pgppBjWncgb5p.pgp
Description: PGP signature
------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
