isis-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dan Haywood <>
Subject Re: moving to test & production, how to optimise speed of response?
Date Mon, 28 Sep 2015 16:06:41 GMT
There isn't really any list, no.

Actually, on my todo list is to do some performance tuning; things have
certainly slowed down over the last few releases.  I have one or two
theories as to why, but haven't researched them as of yet.

You might want to look configure logging to view all SQL queries and to
search for any occurrences of the N+1 problem; eg configure

log4j.appender.sql.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss.SSS} %m%n


log4j.logger.DataNucleus.Datastore.Native=DEBUG, Console, sql
log4j.logger.DataNucleus.Datastore.Schema=DEBUG, Console, sql

in and then monitor sql.log.  I use baretail (on
windows) which supports highlighting of lines; makes it easy to see which
tables are being hit repeatedly.

Another thing you could explore is to use selective caching, eg using the
QueryResultsCache [1]

HTH (a bit)


On 28 September 2015 at 13:51, Stephen Cameron <>

> Hi,
> I am installing on a test server tomorrow, what can I set to optimise speed
> of response? I was looking that the security module video online and
> thinking: gee that is fast! It would be good to get mine that nippy :)
> I know that there are cache optimisations for Wicket and I see a warning
> that I am working in DEVELOPMENT mode when Jetty starts.
> Just wondering if there is a list anywhere of things to do in the
> switch-over?
> Cheers
> Steve C

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message