Toni, > The thing is that the problem only ocurrs from time to time, and when > high load is sent, > > Is there any way to tune sequoia? Or monitor sequoia when high load is sent ? > > -which are good jvm parameters?any way to monitor jvm ? > I would recommend to use jconsole (http://java.sun.com/developer/technicalArticles/J2SE/jconsole.html) that is shipped since J2SE 5 to monitor your JVM and find out if you have any memory problems. > -how request caché works? > Sequoia has 3 caches as described in sequoia.dtd: " MetadataCache: this cache improves the ResultSet creation time by keeping the various field information with their metadata. It is strongly encouraged to use this cache that reduces both cpu and memory usage. ParsingCache: allows to parse a request only once for all its executions. This reduces the cpu load on the controller. ResultCache: this cache keeps the results associated to a given request. Cache entries can be invalidated according to various policies. This cache reduces the load on the database backends."
I would not recommend to use the result cache if you have memory problems. > -for last,how many queries per second can we achice ? > > The thing is our application works quite bad with high load, and we > have to improve the Database access. > For reads, there is no real limit for queries per second as long as you have enough concurrent queries and enough resources to execute them. Everything depends on your system setup and your workload. Hope this helps, Emmanuel -- Emmanuel Cecchet FTO @ Frog Thinker Open Source Development & Consulting -- Web: http://www.frogthinker.org email: [email protected] Skype: emmanuel_cecchet _______________________________________________ Sequoia mailing list [email protected] http://forge.continuent.org/mailman/listinfo/sequoia
