Toni, > I get what has happenned... > > The thing is that I am doing only SELECT commands, nor transactional > comands, and SELECT commands are not saved in recovery log. > > Do you know how can I know the time spent in this SELECT commands... > > It seems that some commands get stuck a take more that 2 segs to > answer, when we are doing LoadTests.... You can profile SELECT statement execution time using the SQLMonitoring option in your virtual database config file (see sequoia.dtd for details). You can dump query execution time from the Sequoia console. Some possible causes for slow SELECTs are: - large tuples and inappropriate JVM memory settings requiring a lot of garbage collecting, - SELECT statement broadcast if the SQL has side effects that must be performed on every backend, - inappropriate request cache configuration, - missing metadata cache, - backend failure during select, - request invoking a stored procedure that forces a schema refresh.
Keep us posted with your findings, 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
