to start you evaluation: 1) watch the logs, they that the time on them so you can see how long things take on the server you have now. 2) monitor your DB connections and watch the cpu usage for the dB compared to ofbiz. Use Apache httpd for static content for fastest delivery. Next step is to move the DB to a server of its own and have a network that supports the throughput necessary not to slow down ofbiz. You must do DB maintianence on a regular basis.
then look at server load balancing. rajesh_r_j sent the following on 9/1/2008 5:21 PM: > We are having severe performance issue running ofbiz with embedded tomcat. > Currently it struggles to serve 50,000 pages/day (with maximum access > between 7pm -11pm). Our deployment architecture is currently one linux box > (2 GHz single processer, 2 GB RAM, CentOS Linux5) hosting web server (ofbiz > embedded tomcat) and DB (postgresql). > > We are looking to serve 30,000 pages/day with each visit serving > approximately 10 pages, which boils down to serving around 2500 - 3000 > customers/day. To achieve this, we are seriously considering moving to a > better server configuration and at the same time thinking about scaling up > the deployment architecture (using apache for static content, having 2 – 3 > instance of servers running ofbiz and having a different server for DB). > > Being a new bee to ofbiz, I was reading through the forums and > documentations to find out what is the correct approach to achieve the above > and was surprised to see that with one box people have achieved around 1 > million pages/day. > > I would like to find out what will be the best approach for us to take and > also find some cool links/documentation/discussions about scaling up with > ofbiz(embedded tomcat), using apache for static content and separate DB. > > Thanks for the help. > > Raj
