A number to describe the actvity of an IDS database
Hello Spookey.
I would like to ask you something about "the activity" done by an IDS DB.
I'm looking for an indicator (essentialy...a number) that counts all the operation done by an IDS DB.
For example, when I submit an SQL command I immagine that happens something like:
- Parse the text to check for syntax error
- Check if the SQL was previously execute, so you can reuse the parse and the optimization phase
- If not, define the best access path to get the data
- Check if the data are stored in the buffer cache.
- If not, get the index pages (suppose that Optimizer does't use Sequential Scan)
- Put the data in the buffer cache
- Return data to the process
I think that the isamtot column returned by "onstat -p" command is "my number"
Do you think is this correct or have I to sum to this number other values maybe showed by the onstat -p command?
About the "onstat -p" command, the "IBM Informix Dynamic Server Administrator's Reference" says:
The next portion of the -p display tabulates the number of times different ISAM calls were executed.
The calls occur at the lowest level of operation and do not necessarily correspond one-to-one with
SQL statement execution. A single query might generate multiple ISAM calls.
These statistics are gathered across the database server and cannot be used to monitor activity on
a single database unless only one database is active or only one database exists:
isamtot
Is the total number of calls
open
Increments when a tblspace is opened
start
Increments the pointer within an index
read
Increments when the read function is called
write
Increments with each write call
rewrite
Increments when an update occurs
delete
Increments when a row is deleted
Thank you in advance!
Andrea Antonello
Italy
P.S. I don't think that you remember me, but I meet you in January in Strasbourg with J.G.Perrin. I hope you are well...
- Login or register to post comments
- 2450 reads
-
- Email this page
- Printer-friendly version
- Send to friend
- PDF version


















Hi Andrea, Yes, I do
Hi Andrea,
Yes, I do remember you ... sorry for not getting back to you earlier, I'm currently on leave.
"isamtot" is the total number of ISAM operations, it is greater than the sum of the ISAM operations listed in the onstat -p output. However, I'm not clear whether this exactly maps onto what you require.
Can you explain why you want this?
A number to describe the activity of an IDS database
Hi Spokey.
I'm trying "to compare" the performance of our application on different hardware used by our customers.
To do this, I need a "number" that describes the activity done by a DB (supposing that the server is only a DB Server).
If I measure this number on different HW together with CPU load (for example..) I can create a table that defines "a trend", "a baseline"...to size a server for a specific load.
For example, one number can be the sum of SELECT,UPDATE,DELETE,INSERT returned by "onstat -p". But with this number I can't capture all the activity of parsing and retriving data from the disks to the process requiring that data...
I'm hoping that the "ISAM Total" was the sum of every activity done by the DB...but, it's not clear, for me, what is an "ISAM Call".
Thank you for your time, Spokey!
Andrea Antonello
SMC Treviso, Italy
Hi Andrea, I can't really
Hi Andrea,
I can't really share with you a list of the RSAM functions that are included in the count that makes up "ISAM tot", as these are company confidential and not publicly documented. The RSAM functions are, however, all those that are involved with data access operations and are roughly analogous to those documented in the C-ISAM manual. Some of the C-ISAM functions are not needed in the database, the database also has some functions that are not supported by C-ISAM and finally, some equivalent functions might have important differences between C-ISAM and RSAM. However, you will be able to get a feel for what sorts of things will be considered RSAM.
"ISAM tot" is incremented with every RSAM operation, as far as I can tell. There are almost certainly some internal database operations that are not considered RSAM operations. Hence, "ISAM tot" is unlikely to be a completely comprehensive activity indicator. I cannot see any way of you identifying or recording non-RSAM activity, so this may well be the best counter you might have. ;-)
Hope this helps!
I understand...
OK. It's clear. "ISAM tot" is not the number that I'm looking for. I'll use the sum of UPD, DEL, INS and SELECT operations executed plus buffers reads/writes because the same SELECT operation can do more jobs in different DBs, depending by the number of rows returned. I think that this "number" will be good. Finally, it was not my intentions to "learn" something about "confidential and not publicly documented" inside by IBM-Informix :-) Again, thank you and I hope to see you again sometimes in the future...Bye-Bye
Hope it works out for you!
Hope it works out for you! Feel free to let us all know how you got on ... :-)