Help parameters RA_PAGES,RA_THRESHOLD

I have doubts with respect to these parametros, as I should calculate that so that the readings in secueciales in temporary it is mas fast. # Read Ahead Variables #RA_PAGES 4 # Number of pages to attempt to read ahead RA_PAGES 4000 # Number of pages to attempt to read ahead#RA_THRESHOLD 2 # Number of pages left before next group RA_THRESHOLD 2000 # Number of pages left before next group onconfig. nfiguration File: /opt/informixids/etc/onconfig.omicron #************************************************************************** # # INFORMIX SOFTWARE, INC. # # Title: onconfig.omicron # Description: Informix Dynamic Server Configuration Parameters # Elaborado por Angel Ruiz Mayo 1 de 2003 # Actualizaciones #************************************************************************** # Root Dbspace Configuration ROOTNAME rootdbs # Root dbspace nameROOTPATH /dev/inf1/rootdbs # Path for device containing root dbspace ROOTOFFSET 0 # Offset of root dbspace into device (Kbytes) ROOTSIZE 286720 # Size of root dbspace (Kbytes) # Disk Mirroring Configuration Parameters MIRROR 0 # Mirroring flag (Yes = 1, No = 0) MIRRORPATH # Path for device containing mirrored root MIRROROFFSET 0 # Offset into mirrored device (Kbytes) # Physical Log Configuration PHYSDBS phyv1 # Location (dbspace) of physical log PHYSFILE 8014 # Physical log file size (Kbytes) # Logical Log Configuration LOGFILES 60 # Number of logical log files LOGSIZE 4000 # Logical log size (Kbytes) # Diagnostics MSGPATH /opt/informixids/online.log # System message log file path CONSOLE /dev/console # System console message path ALARMPROGRAM /opt/informixids/etc/log_full.sh # Alarm program path TBLSPACE_STATS 1 # Maintain tblspace statistics # System Archive Tape Device TAPEDEV /dev/rmt/0m # Tape device path TAPEBLK 20 # Tape block size (Kbytes) TAPESIZE 23101440 # Maximum amount of data to put on tape (Kbytes) # Log Archive Tape Device LTAPEDEV sigma:/dev/rmt/0m # Log tape device path LTAPEBLK 20 # Log tape block size (Kbytes) LTAPESIZE 1850000 # Max amount of data to put on log tape (Kbytes) # Optical STAGEBLOB # Informix Dynamic Server staging area # System Configuration SERVERNUM 0 # Unique id corresponding to a OnLine instance DBSERVERNAME omicron # Name of default database server DBSERVERALIASES omicron_sh # List of alternate dbservernames #NETTYPE ipcshm,1,100,CPU # Configure poll thread(s) for nettype #NETTYPE soctcp,1,300,NET # Configure poll thread(s) for nettype NETTYPE soctcp,4,60,NET # Configure poll thread(s) for nettype DEADLOCK_TIMEOUT 60 # Max time to wait of lock in distributed env. RESIDENT 1 # Forced residency flag (Yes = 1, No = 0) MULTIPROCESSOR 0 # 0 for single-processor, 1 for multi-processor #NUMCPUVPS 1 # Number of user (cpu) vps VPCLASS cpu,num=1,noage VPCLASS aio,num=10 #VPCLASS aio,num=5 #VPCLASS aio,num=8 SINGLE_CPU_VP 1 # If non-zero, limit number of cpu vps to one#SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vps to one #NOAGE 0 # Process aging #AFF_SPROC 0 # Affinity start processor #AFF_NPROCS 0 # Affinity number of processors # Shared Memory Parameters LOCKS 250000 # Maximum number of locks#BUFFERS 30000 # Maximum number of shared buffers BUFFERS 40000 # Maximum number of shared buffers#BUFFERS 60000 # Maximum number of shared buffers #NUMAIOVPS 2 # Number of IO vps PHYSBUFF 500 # Physical log buffer size (Kbytes) LOGBUFF 64 # Logical log buffer size (Kbytes) CLEANERS 8 # Number of buffer cleaner processes#CLEANERS 4 # Number of buffer cleaner processes #CLEANERS 6 # Number of buffer cleaner processes #CLEANERS 5 # Number of buffer cleaner processes SHMBASE 0x0 # Shared memory base address SHMVIRTSIZE 229376 # initial virtual shared memory segment size#SHMADD 65536 # Size of new shared memory segments (Kbytes) SHMADD 32768 # Size of new shared memory segments (Kbytes) SHMTOTAL 383020 # Total shared memory (Kbytes). 0=>unlimited #SHMTOTAL 0 # Total shared memory (Kbytes). 0=>unlimited CKPTINTVL 240 # Check point interval (in sec) DD_HASHMAX 5 # Hernando G DD_HASHSIZE 107 # Hernando G LRUS 20 # Number of LRU queues#LRUS 60 # Number of LRU queues LRU_MAX_DIRTY 3 # LRU percent dirty begin cleaning limit#LRU_MAX_DIRTY 2 # LRU percent dirty begin cleaning limit #LRU_MAX_DIRTY 4 # LRU percent dirty begin cleaning limit #LRU_MAX_DIRTY 70 # LRU percent dirty begin cleaning limit LRU_MIN_DIRTY 1 # LRU percent dirty end cleaning limit#LRU_MIN_DIRTY 50 # LRU percent dirty end cleaning limit TXTIMEOUT 0x12c # Transaction timeout (in sec) STACKSIZE 64 # Stack size (Kbytes) # System Page Size # BUFFSIZE - OnLine no longer supports this configuration parameter. # To determine the page size used by OnLine on your platform # see the last line of output from the command, 'onstat -b'. # Recovery Variables # OFF_RECVRY_THREADS: # Number of parallel worker threads during fast recovery or an offline restore. # ON_RECVRY_THREADS: # Number of parallel worker threads during an online restore. OFF_RECVRY_THREADS 10 # Default number of offline worker threads ON_RECVRY_THREADS 1 # Default number of online worker threads # Data Replication Variables DRINTERVAL 30 # DR max time between DR buffer flushes (in sec) DRTIMEOUT 30 # DR network timeout (in sec)DRLOSTFOUND /opt/informixids/etc/dr.lostfound # DR lost+found file path # CDR Variables CDR_EVALTHREADS 1,2 # evaluator threads (per-cpu-vp,additional) CDR_DSLOCKWAIT 5 # DS lockwait timeout (seconds) CDR_QUEUEMEM 4096 # Maximum amount of memory for any CDR queue (Kbytes) CDR_NIFCOMPRESS 0 # Link level compression (-1 never, 0 none, 9 max) CDR_SERIAL 0,0 # Serial Column Sequence CDR_DBSPACE # dbspace for syscdr database CDR_QHDR_DBSPACE # CDR queue dbspace (default same as catalog) CDR_QDATA_SBSPACE # CDR queue smart blob space CDR_QDATA_SBFLAGS 0 # Log/no-log (default no log) # Backup/Restore variables BAR_ACT_LOG /opt/informixids/bar_act.log # ON-Bar Log file - not in /tmp please BAR_DEBUG_LOG /opt/informixids/bar_dbug.log # ON-Bar Debug Log - not in /tmp please BAR_MAX_BACKUP 0 BAR_RETRY 1 BAR_NB_XPORT_COUNT 10 BAR_XFER_BUF_SIZE 31 RESTARTABLE_RESTORE on BAR_PROGRESS_FREQ 0 # Informix Storage Manager variables ISM_DATA_POOL ISMData ISM_LOG_POOL ISMLogs # Read Ahead Variables #RA_PAGES 4 # Number of pages to attempt to read ahead RA_PAGES 4000 # Number of pages to attempt to read ahead#RA_THRESHOLD 2 # Number of pages left before next group RA_THRESHOLD 2000 # Number of pages left before next group # DBSPACETEMP: # OnLine equivalent of DBTEMP for SE. This is the list of dbspaces # that the OnLine SQL Engine will use to create temp tables etc. # If specified it must be a colon separated list of dbspaces that exist # when the OnLine system is brought online. If not specified, or if # all dbspaces specified are invalid, various ad hoc queries will create # temporary files in /tmp instead. DBSPACETEMP tempdbs1,tempdbs2 # Default temp dbspaces # DUMP*: # The following parameters control the typ

Generalmente cuando informix va a leer en disco para encontrar un datos, identifica la pagina en la que se encuentra ese dato y lee la pagina completa, como en este caso se le indica que leea 4000 paginas entonces lee las 4000 paguinas siguientes que no necesariamente contienen los mismos datos, ademas de que los datos almacenados no tienen un orden en relacion a la paginacion, por lo que puedes estar leyendo datos innecesarios. Ademas recuerda que otros usuarios pueden estar leyendo otro tipo de informacion, y si no encuentra esa informacion en el shared memory entonces leera otras 4000 paginas. y esto por cada usuario... No quisiera parecer muy contradictorio pero me parace que es necesario que se conozca a fondo la arquitectura de informix y entender claramente la filosofia del funcionamiento del shared memory. Hare algunos comentarios que consirdero podrian estar siendo mal configurados segun su: # HISTORIAL DEL CAMBIO DE PARAMETROS ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > # LRU_MAX_DIRTY 2 3 porque se estaba generando el doble de escrituras LRU vs las de Chunk JGG.- Ambos valores son incorrectos ya que este parametro indica el porcentaje maximo de ocupacion de las colas que controlan el uso de los buffer utilizados, un valor que podria ayudar seria (75) JGG Tambien define el parametro LRU_MIN_DIRTY a un porcentaje de 20 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > # SHMVIRTSIZE 131072 196608 Se incrementa para evitar segmentacion JGG.- El tamaño del segmento inicial se determina en relacion a las definiciones de los parametros del shared memory como son (buffers,locks,physbuff,logbuff,ra_threshold,ra_pages ..........), no es un valor que definas arbitrariamente El tamaño de la memoria utilizada por informix no es estatica y puede crecer mas alla de la que defines en el primer segmento, de acuerdo a como se vayan conectando los usuarios, por lo que no puedes evitar la segmentacion. > # SHMADD 65536 32768 Se dismunuye porque no es necesrio un un valor tan grande. JGG.- Es correcto que no utilices un valor tan grande para aprovechar al maximo todos los segmentos de memoria disponible > # SHMTOTAL 361972 350252 Se disminuye por la misma razon JGG.-Si tienes mas memoria disponible te recomiendo que asignes mas, de lo contrario cuando infomrix necesite mas memoria y tu lo estes limitando, inicia un proceso de swap en algun area temporal del disco, lo que provocara una mayor carga para el disco. Si tu servidor (cpu) esta dedicado a informix, puedes poner un valor de ( 0 ) para que utilice toda la memoria disponible. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > # VPCLASS aio,num=8 5 Con kaio no se requiere tener tantas y mejora rendimiento JGG.- Que metodo de acceso a disco utilizas (Row device o cooked files) y cuantos discos tienes, pero si utilizas este parametro considero que le pongas 2 por cada disco > # VPCLASS aio,num=8 10 Como no mejoro rendimiento se aumenta de 8 a 10 JGG.- No con aumentar los valores a los parametros vas a obtener mejor rendimiento, es necesario que verifique si te van a servir ya que estas desperdiciando recursos del cpu (checa tu metodo de acceso a disco) > # CLEANERS 4 8 y se aumentan para revisar comportamiento de ckpoint JGG.- Depende de cuantas colas definas, pero este valor no necesariamente es determinante para la generacion de check points > #=========================================================================== > # NETTYPE soctcp,4,60,NET 1,300,NET # Se recomienda un socket por cada CPU JGG.- Aqui estas definiendo 4 procesadores virtuales para atender los requerimientos de los usuarios que se conectan a traves de protocolo tcp (La recomendacion es correcta pero se refiere a cada CPU fisica, es decir, por cada procesador fisico, no por cada procesador virtual) > # NETTYPE soctcp,1,300,NET 4,60,NET # No es peor recomendacion no validad JGG.- esto es correcto ya que tu servidor solo tiene un procesador fisico pero ademas necesitas definir otro NETTYPE para la coneccion a traves del shared memory, ya que las aplicaciones como el dbaccess lo utilizan NETTYPE ipcshm,1,300,NET 4,60,NET el valor (300) puedes reducirlos, solo calculo cuantos usuarios se van a conecctar a traves de shared memory ( no cuentes a los que se conectan a traves de soctcp) Ademas debes de definir este metodo en tu archivo (sqlhosts ) Espero te sirva Te recomiedo que le des una leida al manual del adminstrador de informix Escribio Jorge Garcia Quintana Roo Mexico ----- Original Message ----- From: "ANGEL MARIA...." <angruiz@coomevamail.com> To: <ids@iiug.org> Sent: Friday, February 27, 2004 2:16 PM Subject: Help parameters RA_PAGES,RA_THRESHOLD [2584] > I have doubts with respect to these parametros, as I should calculate that so that the readings in secueciales in temporary it is mas fast. > > # Read Ahead Variables > #RA_PAGES 4 # Number of pages to attempt to read ahead > RA_PAGES 4000 # Number of pages to attempt to read ahead> #RA_THRESHOLD 2 # Number of pages left before next group > RA_THRESHOLD 2000 # Number of pages left before next group> > onconfig. > nfiguration File: /opt/informixids/etc/onconfig.omicron > #************************************************************************** > # > # INFORMIX SOFTWARE, INC. > # > # Title: onconfig.omicron > # Description: Informix Dynamic Server Configuration Parameters > # Elaborado por Angel Ruiz Mayo 1 de 2003 > # Actualizaciones > #************************************************************************** > > # Root Dbspace Configuration > > ROOTNAME rootdbs # Root dbspace name> ROOTPATH /dev/inf1/rootdbs # Path for device containing root dbspace > ROOTOFFSET 0 # Offset of root dbspace into device (Kbytes) > ROOTSIZE 286720 # Size of root dbspace (Kbytes)> > # Disk Mirroring Configuration Parameters > > MIRROR 0 # Mirroring flag (Yes = 1, No = 0) > MIRRORPATH # Path for device containing mirrored root > MIRROROFFSET 0 # Offset into mirrored device (Kbytes)> > # Physical Log Configuration > > PHYSDBS phyv1 # Location (dbspace) of physical log > PHYSFILE 8014 # Physical log file size (Kbytes)> > # Logical Log Configuration > > LOGFILES 60 # Number of logical log files > LOGSIZE 4000 # Logical log size (Kbytes)> > # Diagnostics > > MSGPATH /opt/informixids/online.log # System message log file path > CONSOLE /dev/console # System console message path > ALARMPROGRAM /opt/informixids/etc/log_full.sh # Alarm program path > TBLSPACE_STATS 1 # Maintain tblspace statistics> > # System Archive Tape Device > > TAPEDEV /dev/rmt/0m # Tape device path > TAPEBLK 20 # Tape block size (Kbytes) > TAPESIZE 23101440 # Maximum amount of data to put on tape (Kbytes)> > # Log Archive Tape Device > > LTAPEDEV sigma:/dev/rmt/0m # Log tape device path > LTAPEBLK 20 # Log tape block size (Kbytes) > LTAPESIZE 1850000 # Max amount of data to put on log tape (Kbytes)> > # Optical > > STAGEBLOB # Informix Dynam

All I can say to 4000 / 2000 is ... AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAARGH! Don't do it! Try 16/4. -- Bye now, Obnoxio "C'est pas parce qu'on n'a rien à dire qu'il faut fermer sa gueule" - Coluche "Necrophilia means never having to say ... well, anything!" - Captain Pedantic "Ogni uomo mi guarda come se fossi una testa di cazzo" - Marco >From: "ANGEL MARIA...." <angruiz@coomevamail.com> >To: ids@iiug.org >Subject: Help parameters RA_PAGES,RA_THRESHOLD [2584] Date: Fri, 27 Feb >2004 15:16:00 -0500 (EST) >Received: from ace.iiug.org ([216.177.38.212]) by mc1-f4.hotmail.com with >Microsoft SMTPSVC(5.0.2195.6824); Fri, 27 Feb 2004 13:22:22 -0800 >Received: from ace.iiug.org (localhost [127.0.0.1])by ace.iiug.org >(8.12.10-14/8.12.8) with ESMTP id i1RKNlUk000804;Fri, 27 Feb 2004 16:15:06 >-0500 (EST) >Received: (from nobody@localhost)by ace.iiug.org (8.12.10-14/8.12.8/Submit) >id i1RKG0Go000554;Fri, 27 Feb 2004 15:16:00 -0500 (EST) >X-Message-Info: UZmYcfFpTCcodmHSghhhsyxRBX4Ka3Xv >Message-Id: <200402272016.i1RKG0Go000554@ace.iiug.org> >Apparently-To: forum.subscriber@iiug.org >Precedence: bulk >Return-Path: nobody@ace.iiug.org >X-OriginalArrivalTime: 27 Feb 2004 21:22:23.0103 (UTC) >FILETIME=[CA2788F0:01C3FD77] > >I have doubts with respect to these parametros, as I should calculate that >so that the readings in secueciales in temporary it is mas fast. > ># Read Ahead Variables >#RA_PAGES 4 # Number of pages to attempt to read ahead >RA_PAGES 4000 # Number of pages to attempt to read ahead>#RA_THRESHOLD 2 # Number of pages left before next group >RA_THRESHOLD 2000 # Number of pages left before next group> >onconfig. >nfiguration File: /opt/informixids/etc/onconfig.omicron >#************************************************************************** ># ># INFORMIX SOFTWARE, INC. ># ># Title: onconfig.omicron ># Description: Informix Dynamic Server Configuration Parameters ># Elaborado por Angel Ruiz Mayo 1 de 2003 ># Actualizaciones >#************************************************************************** > ># Root Dbspace Configuration > >ROOTNAME rootdbs # Root dbspace name>ROOTPATH /dev/inf1/rootdbs # Path for device containing root dbspace >ROOTOFFSET 0 # Offset of root dbspace into device >(Kbytes) >ROOTSIZE 286720 # Size of root dbspace (Kbytes)> ># Disk Mirroring Configuration Parameters > >MIRROR 0 # Mirroring flag (Yes = 1, No = 0) >MIRRORPATH # Path for device containing mirrored root >MIRROROFFSET 0 # Offset into mirrored device (Kbytes)> ># Physical Log Configuration > >PHYSDBS phyv1 # Location (dbspace) of physical log >PHYSFILE 8014 # Physical log file size (Kbytes)> ># Logical Log Configuration > >LOGFILES 60 # Number of logical log files >LOGSIZE 4000 # Logical log size (Kbytes)> ># Diagnostics > >MSGPATH /opt/informixids/online.log # System message log file path >CONSOLE /dev/console # System console message path >ALARMPROGRAM /opt/informixids/etc/log_full.sh # Alarm program path >TBLSPACE_STATS 1 # Maintain tblspace statistics> ># System Archive Tape Device > >TAPEDEV /dev/rmt/0m # Tape device path >TAPEBLK 20 # Tape block size (Kbytes) >TAPESIZE 23101440 # Maximum amount of data to put on tape >(Kbytes)> ># Log Archive Tape Device > >LTAPEDEV sigma:/dev/rmt/0m # Log tape device path >LTAPEBLK 20 # Log tape block size (Kbytes) >LTAPESIZE 1850000 # Max amount of data to put on log tape >(Kbytes)> ># Optical > >STAGEBLOB # Informix Dynamic Server staging area > ># System Configuration > >SERVERNUM 0 # Unique id corresponding to a OnLine>instance >DBSERVERNAME omicron # Name of default database server >DBSERVERALIASES omicron_sh # List of alternate dbservernames >#NETTYPE ipcshm,1,100,CPU # Configure poll thread(s) for nettype >#NETTYPE soctcp,1,300,NET # Configure poll thread(s) for nettype >NETTYPE soctcp,4,60,NET # Configure poll thread(s) for nettype >DEADLOCK_TIMEOUT 60 # Max time to wait of lock in distributed >env. >RESIDENT 1 # Forced residency flag (Yes = 1, No = 0) > >MULTIPROCESSOR 0 # 0 for single-processor, 1 for>multi-processor >#NUMCPUVPS 1 # Number of user (cpu) vps >VPCLASS cpu,num=1,noage >VPCLASS aio,num=10 >#VPCLASS aio,num=5 >#VPCLASS aio,num=8 >SINGLE_CPU_VP 1 # If non-zero, limit number of cpu vps to>one >#SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vps to >one > >#NOAGE 0 # Process aging >#AFF_SPROC 0 # Affinity start processor >#AFF_NPROCS 0 # Affinity number of processors > ># Shared Memory Parameters > >LOCKS 250000 # Maximum number of locks>#BUFFERS 30000 # Maximum number of shared buffers >BUFFERS 40000 # Maximum number of shared buffers>#BUFFERS 60000 # Maximum number of shared buffers >#NUMAIOVPS 2 # Number of IO vps >PHYSBUFF 500 # Physical log buffer size (Kbytes) >LOGBUFF 64 # Logical log buffer size (Kbytes) >CLEANERS 8 # Number of buffer cleaner processes>#CLEANERS 4 # Number of buffer cleaner processes >#CLEANERS 6 # Number of buffer cleaner processes >#CLEANERS 5 # Number of buffer cleaner processes >SHMBASE 0x0 # Shared memory base address >SHMVIRTSIZE 229376 # initial virtual shared memory segment>size >#SHMADD 65536 # Size of new shared memory segments >(Kbytes) >SHMADD 32768 # Size of new shared memory segments >(Kbytes) >SHMTOTAL 383020 # Total shared memory (Kbytes). >0=>unlimited >#SHMTOTAL 0 # Total shared memory (Kbytes). >0=>unlimited >CKPTINTVL 240 # Check point interval (in sec) >DD_HASHMAX 5 # Hernando G >DD_HASHSIZE 107 # Hernando G >LRUS 20 # Number of LRU queues>#LRUS 60 # Number of LRU queues >LRU_MAX_DIRTY 3 # LRU percent dirty begin cleaning limit>#LRU_MAX_DIRTY 2 # LRU percent dirty begin cleaning limit >#LRU_MAX_DIRTY 4 # LRU percent dirty begin cleaning limit >#LRU_MAX_DIRTY 70 # LRU percent dirty begin cleaning limit >LRU_MIN_DIRTY 1 # LRU percent dirty end cleaning limit>#LRU_MIN_DIRTY 50 # LRU percent dirty end cleaning limit >TXTIMEOUT 0x12c # Transaction timeout (in sec) >STACKSIZE 64 # Stack size (Kbytes)> ># System Page Size ># BUFFSIZE - OnLine no longer supports this configuration parameter. ># To determine the page size used by OnLine on your platform ># see the last line of output from the command, 'onstat -b'. > > ># Recovery Variables ># OFF_RECVRY_THREADS: ># Number of parallel worker threads during fast recovery or an offline >restore. ># ON_RECVRY_THREADS: ># Number of parallel worker threads during an online restore. > >OFF_RECVRY_THREADS 10 # Default number of offline worker>threads >ON_RECVRY_THREADS 1 # Default number of online worker threads> ># Data Replication Variables >DRINTERVAL 30 # DR max time between DR buffer flushes (in >sec) >DRTIMEOUT 30 # DR network timeout (in sec)>DRLOSTFOUND /opt/informixids/etc/dr.lostfound # DR lost+found file path > ># CDR Variables >CDR_EVALTHREADS 1,2 # evaluator threads (per-cpu-vp,additional)>CDR

I think these Parameters are set much too high. Normally RA_PAGES are set to somewhat between 4 and 128. You can check the usage by looking at "onstat -p": compare: ixda-RA + idx-RA + da-RA with RA-pgsused and you have the usage of your READAHEAD. The Parameter da-RA should be low (this indicates sequential scans from disk). IBM Informix Dynamic Server Version 9.40.UC3 -- On-Line -- Up 1 days 04:00:11 -- 379344 Kbytes Profile dskreads pagreads bufreads Êched dskwrits pagwrits bufwrits Êched 160867 214691 7425580 97.83 419031 506641 788932 46.89 isamtot open start read write rewrite delete commit rollbk 5567766 337817 405797 3429457 35197 78148 2966 34678 12 gp_read gp_write gp_rewrt gp_del gp_alloc gp_free gp_curs 14165 2 26281 1 0 0 2 ovlock ovuserthread ovbuff usercpu syscpu numckpts flushes 0 0 0 320.14 139.86 696 3559 bufwaits lokwaits lockreqs deadlks dltouts ckpwaits compress seqscans 8613 5 3654247 0 0 45 11680 423 ixda-RA idx-RA da-RA RA-pgsused lchwaits 24191 19916 13329 57411 459 ANGEL MARIA.... wrote: >I have doubts with respect to these parametros, as I should calculate that so that the readings in secueciales in temporary it is mas fast. > ># Read Ahead Variables >#RA_PAGES 4 # Number of pages to attempt to read ahead >RA_PAGES 4000 # Number of pages to attempt to read ahead>#RA_THRESHOLD 2 # Number of pages left before next group >RA_THRESHOLD 2000 # Number of pages left before next group> > > -- Gerd Kaluzinski Tel. :+49-(0)7541-585-5000 Manager Consulting Fax :+49-(0)7541-585-5500 BYTEC GmbH mailto:support@bytec.de Hermann-Metzger-Str.7 http://www.bytec.de 88045 Friedrichshafen