Yes. But thx for the hint anyway. Just dropped all indexes and dropped all unneeded Classes. No improvement.
My greatest concern lies still with the "ORDER BY" clause. I think, all other queries could be easily improved by horizontal scaling (more server-nodes) and a leaner ClassModel. Our current $ORIENT_HOME/bin/server.sh looks like this: LOG_FILE=$ORIENTDB_HOME/config/orientdb-server-log.properties WWW_PATH=$ORIENTDB_HOME/www ORIENTDB_SETTINGS="-Dprofiler.enabled=true -XX:+AggressiveOpts -XX:CompileThreshold=200 -XX:+PerfDisableSharedMem" JAVA_OPTS_SCRIPT="-Djna.nosys=true -XX:+HeapDumpOnOutOfMemoryError -Djava.awt.headless=true -Dfile.encoding=UTF8 -Drhino.opt.level=9" # -Ddb.mvcc=true -Dstorage.useWAL=false -Dstorage.wal.syncOnPageFlush=false # ORIENTDB MAXIMUM HEAP. USE SYNTAX -Xmx<memory>, WHERE <memory> HAS THE TOTAL MEMORY AND SIZE UNIT. EXAMPLE: -Xmx512m MAXHEAP="-Xmx512m" # ORIENTDB MAXIMUM DISKCACHE IN MB, EXAMPLE, ENTER -Dstorage.diskCache.bufferSize=8192 FOR 8GB MAXDISKCACHE="-Dstorage.diskCache.bufferSize=12288" MAXHEAP and MAXDISKCACHE sizes are okay for 16GB of RAM? Regards & thxs, Sebastian On Wednesday, July 29, 2015 at 1:35:59 PM UTC+2, scott molinari wrote: > > Have you seen this page? > http://orientdb.com/docs/last/Performance-Tuning.html > > Scott > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
