iReach bad performance

Hi, I have just ported my local intranet from IIS on a Windows NT 4.0 server to iReach on a SUN Ultra Enterprice 3500 with Solaris 2.6. I am using the IPlanet web server from Netscape and the drivernsapi35.so to connect to the Informix OnLine version 9.14.uc6. I have allocated 82Mb of memory to the Informix OnLine server (BUFFERS=20480). My problem is, that the iReach solutions performance is bad. To load my main intranet page the iReach solution takes 4 sec. On IIS the main page is ready in fractions of a second. What can I do to increase the performance ? Regards Poul Pedersen Kuwait Petroleum (Danmark) A/S

"Poul Pedersen" <pp@q8.dk> writes: > Hi, > > I have just ported my local intranet from IIS on a Windows NT 4.0 server to > iReach on a SUN Ultra Enterprice > 3500 with Solaris 2.6. I am using the IPlanet web server from Netscape and > the drivernsapi35.so to connect to the > Informix OnLine version 9.14.uc6. I have allocated 82Mb of memory to the > Informix OnLine server (BUFFERS=20480). > > My problem is, that the iReach solutions performance is bad. To load my main > intranet page the iReach solution > takes 4 sec. On IIS the main page is ready in fractions of a second. > > What can I do to increase the performance ? Have you done UPDATE STATISTICS? Thomas

Hi Thomas Thanks for your email. Yes "update statistics high" - The time decreased from 5 to 4 sec. Regards Poul Pedersen Thomas Parsli <thomas.parsli@startsiden.no> wrote in message news:bt3e5kiz.fsf@ss1.nextel.no... > "Poul Pedersen" <pp@q8.dk> writes: > > > Hi, > > > > I have just ported my local intranet from IIS on a Windows NT 4.0 server to > > iReach on a SUN Ultra Enterprice > > 3500 with Solaris 2.6. I am using the IPlanet web server from Netscape and > > the drivernsapi35.so to connect to the > > Informix OnLine version 9.14.uc6. I have allocated 82Mb of memory to the > > Informix OnLine server (BUFFERS=20480). > > > > My problem is, that the iReach solutions performance is bad. To load my main > > intranet page the iReach solution > > takes 4 sec. On IIS the main page is ready in fractions of a second. > > > > What can I do to increase the performance ? > > Have you done UPDATE STATISTICS? > > Thomas

The ONCONFIG file is: #************************************************************************** # # INFORMIX SOFTWARE, INC. # # Title: onconfig.std # Description: INFORMIX-Universal Server Configuration Parameters # #************************************************************************** # Root Dbspace Configuration ROOTNAME tb80root1dbs # Root dbspace nameROOTPATH /usr/Informix/dev/tb80root1dsk # Path for device containing root dbspace ROOTOFFSET 0 # Offset of root dbspace into device (Kbytes) ROOTSIZE 500000 # 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 tb80root1dbs # Location (dbspace) of physical log PHYSFILE 50000 # Physical log file size (Kbytes) # Logical Log Configuration LOGFILES 6 # Number of logical log files LOGSIZE 20480 # Logical log size (Kbytes) # Diagnostics MSGPATH /usr/Informix2/tb80.log # System message log file path CONSOLE /usr/Informix2/tb80.con # System console message path ALARMPROGRAM /usr/Informix2/etc/log_full.sh # Alarm program path # System Archive Tape Device #TAPEDEV /dev/rmt/0 # Tape device path TAPEDEV /usr/Informix2/dev/tb80arc.tape TAPEBLK 16 # Tape block size (Kbytes) TAPESIZE 20000000 # Maximum amount of data to put on tape (Kbytes) # Log Archive Tape Device LTAPEDEV /dev/null # Log tape device path LTAPEBLK 16 # Log tape block size (Kbytes) LTAPESIZE 2000000 # Max amount of data to put on log tape (Kbytes) # Optical STAGEBLOB # INFORMIX-OnLine/Universal Server staging area # System Configuration SERVERNUM 80 # Unique id corresponding to a OnLineinstance DBSERVERNAME tb80 # Name of default database server DBSERVERALIASES tb80shm # List of alternate dbservernames DEADLOCK_TIMEOUT 60 # Max time to wait of lock in distributed env. RESIDENT 0 # Forced residency flag (Yes = 1, No = 0) MULTIPROCESSOR 0 # 0 for single-processor, 1 formulti-processor NUMCPUVPS 0 # Number of user (cpu) vps# Lajo 01-03-2000 We do only have ONE CPU !!! #SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vps to one SINGLE_CPU_VP 1 # If non-zero, limit number of cpu vps toone NOAGE 0 # Process aging AFF_SPROC 0 # Affinity start processor AFF_NPROCS 0 # Affinity number of processors # Shared Memory Parameters # Lajo 01/03-2000 - Uses WAY TO MUCH MEMORY on Alhena!!! #LOCKS 20000 # Maximum number of locks #BUFFERS 50000 # Maximum number of shared buffers LOCKS 32768 # Maximum number of locks BUFFERS 20480 # Maximum number of shared buffers# BUFFERS 50000 # Maximum number of shared buffers NUMAIOVPS # Number of IO vps PHYSBUFF 1024 # Physical log buffer size (Kbytes) LOGBUFF 1024 # Logical log buffer size (Kbytes)LOGSMAX 50 # Maximum number of logical log files CLEANERS 4 # Number of buffer cleaner processes SHMBASE 0xa000000 # Shared memory base address#SHMBASE 0xa000000 # Shared memory base address SHMVIRTSIZE 32768 # initial virtual shared memory segment size SHMADD 8192 # Size of new shared memory segments (Kbytes) SHMTOTAL 0 # Total shared memory (Kbytes). 0=>unlimited CKPTINTVL 3600 # Check point interval (in sec) LRUS 8 # Number of LRU queues LRU_MAX_DIRTY 2 # LRU percent dirty begin cleaning limit LRU_MIN_DIRTY 1 # LRU percent dirty end cleaning limit LTXHWM 50 # Long transaction high water markpercentage LTXEHWM 60 # Long transaction high water mark (exclusive) TXTIMEOUT 0x12c # Transaction timeout (in sec) STACKSIZE 32 # 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 workerthreads ON_RECVRY_THREADS 1 # Default number of online worker threads # Data Replication Variables # DRAUTO: 0 manual, 1 retain type, 2 reverse type DRAUTO 0 # DR automatic switchover DRINTERVAL 30 # DR max time between DR buffer flushes (in sec) DRTIMEOUT 30 # DR network timeout (in sec)DRLOSTFOUND /usr/Informix2/etc/dr.lostfound # DR lost+found file path # Backup/Restore variables BAR_ACT_LOG /tmp/bar_act.log BAR_MAX_BACKUP 0 BAR_RETRY 1 BAR_NB_XPORT_COUNT 10 BAR_XFER_BUF_SIZE 31 # Read Ahead Variables RA_PAGES # Number of pages to attempt to read ahead RA_THRESHOLD # 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 tb80tmp1dbs # Default temp dbspaces # DUMP*: # The following parameters control the type of diagnostics information which # is preserved when an unanticipated error condition (assertion failure) occurs # during OnLine operations. # For DUMPSHMEM, DUMPGCORE and DUMPCORE 1 means Yes, 0 means No. DUMPDIR /tmp # Preserve diagnostics in this directory DUMPSHMEM 1 # Dump a copy of shared memory DUMPGCORE 0 # Dump a core image using 'gcore' DUMPCORE 0 # Dump a core image (Warning:this aborts OnLine) DUMPCNT 1 # Number of shared memory or gcore dumps for # a single user's session FILLFACTOR 90 # Fill factor for building indexes # method for OnLi

"Poul Pedersen" <pp@q8.dk> writes: > Hi Thomas > > Thanks for your email. Yes "update statistics high" - The time decreased > from 5 to 4 sec. Ok, are you _shure_ it's the database? Test your SQL from ie. dbaccess. If there's a lot of sorting you might have to do some tuning, but this amount of increase (5-10 times) sounds like lack of indexes, update statistics, wrong parameters or just slow hardware. Do a good UPDATE STATISTICS with ie. the clowns package: ftp://ftp.iiug.org/pub/informix/pub/mkupdstats.gz Thomas

Here goes, see below. Before I start I can tell you you do not have enough buffers but to be sure post the output of onstat -p and the number of minutes since you last ran onstat -z if after engine startup. Alos post onstat -d, onstat -D, onstat -g iov, onstat -g iof, and onstat -F. Poul Pedersen wrote: > The ONCONFIG file is: > #************************************************************************** > # > # INFORMIX SOFTWARE, INC. > # > # Title: onconfig.std > # Description: INFORMIX-Universal Server Configuration Parameters > # > #************************************************************************** > > # Root Dbspace Configuration > > ROOTNAME tb80root1dbs # Root dbspace name> ROOTPATH /usr/Informix/dev/tb80root1dsk > # Path for device containing root dbspace > ROOTOFFSET 0 # Offset of root dbspace into device > (Kbytes) > ROOTSIZE 500000 # 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 tb80root1dbs # Location (dbspace) of physical log > PHYSFILE 50000 # Physical log file size (Kbytes)> First problem, physical logs in ROOTNAME is a performance no-no. > > # Logical Log Configuration > > LOGFILES 6 # Number of logical log files > LOGSIZE 20480 # Logical log size (Kbytes)> You will likely need many more logs but that is not a performance issue. Having the logs on the same dbspace or even the same drive as physical log and/or rootdbs IS a performance problem, but I cannot tell that now. > > # Diagnostics > > MSGPATH /usr/Informix2/tb80.log # System message log file path > CONSOLE /usr/Informix2/tb80.con # System console message path > ALARMPROGRAM /usr/Informix2/etc/log_full.sh # Alarm program path > > # System Archive Tape Device > > #TAPEDEV /dev/rmt/0 # Tape device path > TAPEDEV /usr/Informix2/dev/tb80arc.tape > TAPEBLK 16 # Tape block size (Kbytes) > TAPESIZE 20000000 # Maximum amount of data to put on tape > (Kbytes)> > # Log Archive Tape Device > > LTAPEDEV /dev/null # Log tape device path > LTAPEBLK 16 # Log tape block size (Kbytes) > LTAPESIZE 2000000 # Max amount of data to put on log tape > (Kbytes)> PLEASE do not throw your logs away! There are several schemes for painlessly backing up your logfiles. Scan this newsgroup's history on the IIUG site for some and manuals for others, but do backup your logs. You will be glad you did. > > # Optical > > STAGEBLOB # INFORMIX-OnLine/Universal Server staging > area > > # System Configuration > > SERVERNUM 80 # Unique id corresponding to a OnLine> instance > DBSERVERNAME tb80 # Name of default database server > DBSERVERALIASES tb80shm # List of alternate dbservernames > DEADLOCK_TIMEOUT 60 # Max time to wait of lock in distributed > env. > RESIDENT 0 # Forced residency flag (Yes = 1, No = 0) > > MULTIPROCESSOR 0 # 0 for single-processor, 1 for> multi-processor > NUMCPUVPS 0 # Number of user (cpu) vps> # Lajo 01-03-2000 We do only have ONE CPU !!! > #SINGLE_CPU_VP 0 # If non-zero, limit number of cpu vps to > one > SINGLE_CPU_VP 1 # If non-zero, limit number of cpu vps to> one > > NOAGE 0 # Process aging> NOAGE is important on Solaris. Turn it on. > AFF_SPROC 0 # Affinity start processor > AFF_NPROCS 0 # Affinity number of processors> > # Shared Memory Parameters > > # Lajo 01/03-2000 - Uses WAY TO MUCH MEMORY on Alhena!!! > #LOCKS 20000 # Maximum number of locks > #BUFFERS 50000 # Maximum number of shared buffers > LOCKS 32768 # Maximum number of locks > BUFFERS 20480 # Maximum number of shared buffers I suspect you need MANY more BUFFERS, post the onstats suggested above and we'll see. > > # BUFFERS 50000 # Maximum number of shared buffers > NUMAIOVPS # Number of IO vps > PHYSBUFF 1024 # Physical log buffer size (Kbytes) > LOGBUFF 1024 # Logical log buffer size (Kbytes)> LOGSMAX 50 # Maximum number of logical log files > CLEANERS 4 # Number of buffer cleaner processes CLEANERS should be >= LRUS you need at least 8 for the LRUS value below. Until we see your onstat output I cannot recommend changing LRUS. > > SHMBASE 0xa000000 # Shared memory base address> #SHMBASE 0xa000000 # Shared memory base address > SHMVIRTSIZE 32768 # initial virtual shared memory segment size > SHMADD 8192 # Size of new shared memory segments > (Kbytes) > SHMTOTAL 0 # Total shared memory (Kbytes). 0=>unlimited > CKPTINTVL 3600 # Check point interval (in sec) > LRUS 8 # Number of LRU queues > LRU_MAX_DIRTY 2 # LRU percent dirty begin cleaning limit > LRU_MIN_DIRTY 1 # LRU percent dirty end cleaning limit > LTXHWM 50 # Long transaction high water mark> percentage > LTXEHWM 60 # Long transaction high water mark > (exclusive) > TXTIMEOUT 0x12c # Transaction timeout (in sec) > STACKSIZE 32 # 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 > # DRAUTO: 0 manual, 1 retain type, 2 reverse type > DRAUTO 0 # DR automatic switchover > DRINTERVAL 30 # DR max time between DR buffer flushes (in > sec) > DRTIMEOUT 30 # DR network timeout (in sec)> DRLOSTFOUND /usr/Informix2/etc/dr.lostfound # DR lost+found file path > > # Backup/Restore variables > BAR_ACT_LOG /tmp/bar_act.log > BAR_MAX_BACKUP 0 > BAR_

Thanks Art Well, I changed the number of buffers from 20480 to 100000, but there was no change in the refresh-time for the main intranet web page (4 sec.). (NOAGE changed from 0 to 1, CLEANERS changed from 4 to 8.) In general it is correct, that the physical/logical logs must not be placed in the root dbspace. The raw devices are striped on 3 physical disks. The disks are mirrored on 3 other disks. I am using dual optical interfaces to the disks. I tryed to initiate a test with onstat -z after loading og the main intranet page. The following data are for one single refresh of this page ! I am surprised to see, that this single refresh generated 7656 bufreads and 805 dskwrits of which 800 was to the tmp dbspace ! A test with /tmp instead of a tmp dbspace showed no change in the 4 sec. responce time, the read-cache percent in this case is 100.00%. Regards Poul Pedersen INFORMIX-Universal Server Version 9.14.UC6 -- On-Line -- Up 00:01:43 -- 248648 Kbytes Profile dskreads pagreads bufreads %cached dskwrits pagwrits bufwrits %cached 50 800 7656 99.35 51 805 217 76.50 isamtot open start read write rewrite delete commit rollbk 7782 92 994 2861 12 0 12 1 0 gp_read gp_write gp_rewrt gp_del gp_alloc gp_free gp_curs 7 0 0 0 0 0 0 ovlock ovuserthread ovbuff usercpu syscpu numckpts flushes 0 0 0 2.32 0.05 0 0 bufwaits lokwaits lockreqs deadlks dltouts ckpwaits compress seqscans 0 0 379 0 0 0 11 32 ixda-RA idx-RA da-RA RA-pgsused lchwaits 0 0 0 0 0 >onstat -D INFORMIX-Universal Server Version 9.14.UC6 -- On-Line -- Up 00:07:54 -- 248648 Kbytes Dbspaces address number flags fchunk nchunks flags owner name 17392148 1 1 1 1 N informix tb80root1dbs 173928e0 2 1 2 1 N informix tb80data1dbs 17392958 3 8000 3 1 N S informix tb80sblob1dbs 173929d0 4 2001 4 1 N T informix tb80tmp1dbs 4 active, 2047 maximum Chunks address chk/dbs offset page Rd page Wr pathname 173921c0 1 1 0 0 5 /usr/Informix/dev/tb80root1dsk 17392658 2 2 0 0 0 /usr/Informix/dev/tb80data1dsk 17392730 3 3 0 0 0 /usr/Informix/dev/tb80sblob1dsk 17392808 4 4 0 800 800 /usr/Informix/dev/tb80tmp1dsk 4 active, 2047 maximum INFORMIX-Universal Server Version 9.14.UC6 -- On-Line -- Up 00:13:33 -- 248648 Kbytes Physical Logging Buffer bufused bufsize numpages numwrits pages/io P-1 5 512 0 0 0.00 phybegin physize phypos phyused %used 10003f 25000 12786 5 0.02 Logical Logging Buffer bufused bufsize numrecs numpages numwrits recs/pages pages/io L-3 0 512 50 5 1 10.0 5.0 Subsystem numrecs Log Space used OLDRSAM 50 9384 address number flags uniqid begin size used %used a1d3970 1 F------ 0 1061e7 10240 0 0.00 a1d398c 2 F------ 0 1089e7 10240 0 0.00 a1d39a8 3 F------ 0 10b1e7 10240 0 0.00 a1d39c4 4 F------ 0 10d9e7 10240 0 0.00 a1d39e0 5 F------ 0 1101e7 10240 0 0.00 a1d39fc 6 U---C-L 36 1129e7 10240 3407 33.27 INFORMIX-Universal Server Version 9.14.UC6 -- On-Line -- Up 00:14:05 -- 248648 Kbytes Dbspaces address number flags fchunk nchunks flags owner name 17392148 1 1 1 1 N informix tb80root1dbs 173928e0 2 1 2 1 N informix tb80data1dbs 17392958 3 8000 3 1 N S informix tb80sblob1dbs 173929d0 4 2001 4 1 N T informix tb80tmp1dbs 4 active, 2047 maximum Chunks address chk/dbs offset size free bpages flags pathname 173921c0 1 1 0 250000 161528 PO- /usr/Informix/dev/tb8 0root1dsk 17392658 2 2 0 250000 236707 PO- /usr/Informix/dev/tb8 0data1dsk 17392730 3 3 0 500000 276410 461877 POS /usr/Informix/dev/tb8 0sblob1dsk 17392808 4 4 0 125000 124947 PO- /usr/Informix/dev/tb8 0tmp1dsk 4 active, 2047 maximum onstat -g iof INFORMIX-Universal Server Version 9.14.UC6 -- On-Line -- Up 00:14:26 -- 248648 Kbytes AIO global files: gfd pathname totalops dskread dskwrite io/s 3 tb80root1dsk 1 0 1 0.0 4 tb80data1dsk 0 0 0 0.0 5 tb80sblob1dsk 0 0 0 0.0 6 tb80tmp1dsk 100 50 50 0.1 onstat -F INFORMIX-Universal Server Version 9.14.UC6 -- On-Line -- Up 00:14:49 -- 248648 Kbytes Fg Writes LRU Writes Chunk Writes 0 0 0 address flusher state data 1739453c 0 I 0 = 0X0 17394a60 1 I 0 = 0X0 17394f84 2 I 0 = 0X0 173954a8 3 I 0 = 0X0 173959cc 4 I 0 = 0X0 17395ef0 5 I 0 = 0X0 17396414 6 I 0 = 0X0 17396938 7 I 0 = 0X0 states: Exit Idle Chunk Lru >onstat -u INFORMIX-Universal Server Version 9.14.UC6 -- On-Line -- Up 00:15:23 -- 248648 Kbytes Userthreads address flags sessid user tty wait tout locks nreads nwrites 17394018 ---P--D 1 informix - 0 0 0 0 0 1739453c ---P--F 0 informix - 0 0 0 0 0 17394a60 ---P--F 0 informix - 0 0 0 0 0 17394f84 ---P--F 0 informix - 0 0 0 0 0 173954a8 ---P--F 0 informix - 0 0 0 0 0 173959cc ---P--F 0 informix - 0 0 0 0 0 17395ef0 ---P--F 0 informix - 0 0 0 0 0 17396414 ---P--F 0 informix - 0 0 0 0 0 17396938 ---P--F 0 informix - 0 0 0 0 0 17396e5c ---P--- 9 informix - 0 0 0 0 0 17397380 ---P--B 10 informix - 0 0 0 0 0 173978a4 ---P--D 12 informix - 0 0 0 0 0 17397dc8 Y--P--- 14 intranet - 17594890 0 1 0 0 173982ec Y--P--- 6 intranet - 17535d78 0 1 800 805 14 active, 128 total, 0 maximum concurrent Art S. Kagel <kagel@bloomberg.net> wrote in message news:38F5F98C.6B1EA0D@bloomberg.net... > Here

Poul Pedersen wrote: > Thanks Art > > Well, I changed the number of buffers from 20480 to 100000, but there was no > change in the refresh-time for the > main intranet web page (4 sec.). (NOAGE changed from 0 to 1, CLEANERS > changed from 4 to 8.) > > In general it is correct, that the physical/logical logs must not be placed > in the root dbspace. The raw devices are striped on 3 physical disks. The > disks are mirrored on 3 other disks. I am using dual optical interfaces to > the disks. There have been reports of poor performance from the A5000 arrays but I'm not going to blame that right off. The onstat -p shows 32 sequential scans and 379 lock requests for your small query (only 800 pages actually loaded from disk and rescanned 7656 times). Either iReach is generating really poor queries or you need to add an index or two somewhere, or both I guess. Art S. Kagel > > > I tryed to initiate a test with onstat -z after loading og the main intranet > page. The following data are for one single > refresh of this page ! I am surprised to see, that this single refresh > generated 7656 bufreads and 805 dskwrits of which > 800 was to the tmp dbspace ! A test with /tmp instead of a tmp dbspace > showed no change in the 4 sec. responce time, the read-cache percent in this > case is 100.00%. > > Regards > Poul Pedersen > > INFORMIX-Universal Server Version 9.14.UC6 -- On-Line -- Up 00:01:43 -- > 248648 > Kbytes > > Profile > dskreads pagreads bufreads %cached dskwrits pagwrits bufwrits %cached > 50 800 7656 99.35 51 805 217 76.50 > > isamtot open start read write rewrite delete commit > rollbk > 7782 92 994 2861 12 0 12 1 0 > > gp_read gp_write gp_rewrt gp_del gp_alloc gp_free gp_curs > 7 0 0 0 0 0 0 > > ovlock ovuserthread ovbuff usercpu syscpu numckpts flushes > 0 0 0 2.32 0.05 0 0 > > bufwaits lokwaits lockreqs deadlks dltouts ckpwaits compress seqscans > 0 0 379 0 0 0 11 32 > > ixda-RA idx-RA da-RA RA-pgsused lchwaits > 0 0 0 0 0 > > >onstat -D> > INFORMIX-Universal Server Version 9.14.UC6 -- On-Line -- Up 00:07:54 -- > 248648 > Kbytes > > Dbspaces > address number flags fchunk nchunks flags owner name > 17392148 1 1 1 1 N informix tb80root1dbs > 173928e0 2 1 2 1 N informix tb80data1dbs > 17392958 3 8000 3 1 N S informix tb80sblob1dbs > 173929d0 4 2001 4 1 N T informix tb80tmp1dbs > 4 active, 2047 maximum > > Chunks > address chk/dbs offset page Rd page Wr pathname > 173921c0 1 1 0 0 5 /usr/Informix/dev/tb80root1dsk > 17392658 2 2 0 0 0 /usr/Informix/dev/tb80data1dsk > 17392730 3 3 0 0 0 /usr/Informix/dev/tb80sblob1dsk > 17392808 4 4 0 800 800 /usr/Informix/dev/tb80tmp1dsk > 4 active, 2047 maximum > > INFORMIX-Universal Server Version 9.14.UC6 -- On-Line -- Up 00:13:33 -- > 248648 > Kbytes > > Physical Logging > Buffer bufused bufsize numpages numwrits pages/io > P-1 5 512 0 0 0.00 > phybegin physize phypos phyused %used > 10003f 25000 12786 5 0.02 > > Logical Logging > Buffer bufused bufsize numrecs numpages numwrits recs/pages pages/io > L-3 0 512 50 5 1 10.0 5.0 > Subsystem numrecs Log Space used > OLDRSAM 50 9384 > > address number flags uniqid begin size used %used > a1d3970 1 F------ 0 1061e7 10240 0 0.00 > a1d398c 2 F------ 0 1089e7 10240 0 0.00 > a1d39a8 3 F------ 0 10b1e7 10240 0 0.00 > a1d39c4 4 F------ 0 10d9e7 10240 0 0.00 > a1d39e0 5 F------ 0 1101e7 10240 0 0.00 > a1d39fc 6 U---C-L 36 1129e7 10240 3407 33.27 > > INFORMIX-Universal Server Version 9.14.UC6 -- On-Line -- Up 00:14:05 -- > 248648 > Kbytes > > Dbspaces > address number flags fchunk nchunks flags owner name > 17392148 1 1 1 1 N informix tb80root1dbs > 173928e0 2 1 2 1 N informix tb80data1dbs > 17392958 3 8000 3 1 N S informix tb80sblob1dbs > 173929d0 4 2001 4 1 N T informix tb80tmp1dbs > 4 active, 2047 maximum > > Chunks > address chk/dbs offset size free bpages flags pathname > 173921c0 1 1 0 250000 161528 PO- > /usr/Informix/dev/tb8 > 0root1dsk > 17392658 2 2 0 250000 236707 PO- > /usr/Informix/dev/tb8 > 0data1dsk > 17392730 3 3 0 500000 276410 461877 POS > /usr/Informix/dev/tb8 > 0sblob1dsk > 17392808 4 4 0 125000 124947 PO- > /usr/Informix/dev/tb8 > 0tmp1dsk > 4 active, 2047 maximum > > onstat -g iof> > INFORMIX-Universal Server Version 9.14.UC6 -- On-Line -- Up 00:14:26 -- > 248648 > Kbytes > > AIO global files: > gfd pathname totalops dskread dskwrite io/s > 3 tb80root1dsk 1 0 1 0.0 > 4 tb80data1dsk 0 0 0 0.0 > 5 tb80sblob1dsk 0 0 0 0.0 > 6 tb80tmp1dsk 100 50 50 0.1 > > onstat -F> > INFORMIX-Universal Server Version 9.14.UC6 -- On-Line -- Up 00:14:49 -- > 248648 > Kbytes > > Fg Writes LRU Writes Chunk Writes > 0 0 0 > > address flusher state data > 1739453c 0 I 0 = 0X0 > 17394a60 1 I 0 = 0X0 > 17394f84 2 I 0 = 0X0 > 173954a8 3 I 0 = 0X0 > 173959cc 4 I 0 = 0X0 > 17395ef0 5 I 0 = 0X0 > 17396414 6 I 0 = 0X0 > 17396938 7 I 0 = 0X0 > states: Exit Idle Chunk Lru > > >onstat -u> > INFORMIX-Universal Server Version 9.14.UC6 -- On-Line -- Up 00:15:23 -- > 248648 > Kbytes > > Userthreads > address flags sessid user tty wait tout locks nreads > nwrites > 17394018 ---P--D 1 informix - 0 0 0 0 0 > 1739453c ---P--F 0 informix - 0 0 0 0 0 > 17394a60 ---P--F 0 informix - 0 0 0 0 0 > 17394f84 ---P--F 0 informix - 0 0 0 0 0 > 173954a8 ---P--F 0 informix - 0 0 0 0 0 > 173959cc ---P--F 0 informix - 0 0 0 0 0 > 17395ef0 ---