Have charts rendered by another webapp

[romain.pennes@foederis.fr]

Hello, As of now, Rollbase is built on different components, separated in different webapps : Master (master.war) : ISV management of customer zones Production (prod1.war) : Production front-end service for most user requests of a customer zone REST (rest.war) : REST Web Services RSS (rss.war) : RSS web feeds Router (router.war) : To direct a user to its production server and database Search (search.war) : Lucene indexing and searching SOAP (webapi.war) : SOAP Web Services Storage (storage.war) : To store/retrieve files and process imports Workflow (workflow.war) : Technical Rollbase queuing management In Private Cloud, it is possible to have a cluster environment allowing to separate components onto different Tomcat instances. Having "Production" component alone in aTomcat instance allows front-end operations to be separated from all the other components operations which helps having better performance and faster page render-time. ------------------------------------------------------------------------------------------------------------------------------------------------------ We noticed that some operations performed by Production component consume a lot of resources, thus impacting performance of the whole Tomcat instance and affecting all users. These operations should be processed by another component (webapp), so we could install it on another Tomcat Instance. Chart rendering (When more that 20.000 records are present in an object) and a fusion chart is rendered, it takes 100% of CPU for more than 5-10 secs). This means absolutely no user in any customer zone can use the app in the mean time. Formula parsing When having advanced triggers and formulas, it can take a few seconds to process. There again, 100% of CPU is being used and the app is absolutely not useable by any other user in any customer zone. The most penalizing for us is clearly Chart rendering. We Thanks, Romain Pennes.

Continue reading...