> ps is showing so many entries of tomcat and mysql even when not busy. Is this > normal? > What else is needed? > > There are certain resource limitations for me (see user_beancounters). Which > of these limitations does magnolia influence? Maybe there are minimum > requirements for magnolia on a system with certain parallel visitors?
Speed of processing is mainly function of the number of parallel requests. The memory consumed by Magnolia is mainly dependent on the kind of content that is being served rather then on number of parallel requests. This is specially true for the public instance. > > I would prefer to configure the system to work with mysql instead of > switching to the file based solution. > Isn't it the job of magnolia to handle new mysql connections with care? Can't speak for MySQL, but I guess what you see for tomcat is one thread per http listener (I believe tomcat keeps min 25 free by default) plus of course if you have other then just http connectors there will be some threads spawned by that too and there is also bunch of thread that Tomcat uses for other internal work. As for connections, you have deployed Magnolia with JackRabbit as a JCR backend, and it is a JackRabbit that is managing DB connections. JackRabbit uses long living connections, so there will be one connection opened (on startup) per workspace. To see the total number of connections you can expect look at repositories/magnolia/workspaces folder and count the subdirectories there. HTH, Jan ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
