Conference ulysse::rdb_vms_competition

213.0. "Oracle: locking tables in memory?" by TROU02::SPACKMAN () Tue Oct 11 1988 20:37

	I am currently involved in a benchmark of Rdb V3.0 against Oracle
(V6 is obviously being used). We suspect that they are locking one
particular table in memory to improve their timings on a variety of queries
that make use of that table. Can anyone provide information on how this
locking works in terms of whether the lock is in place for the life of a
transaction or the life of the BIND or until there no longer any users in
the database? Is the lock applicable to just the user who issued it, or to 
all users, since they do support global caching? I am trying to evaluate the
applicability of this feature in a production environment & have not been
able to find any reference to it in any of the competitive information I
have seen ... meaning BUFFER articles, NOTES, etc. 

	Also, is there anything we can do with Rdb to achieve the same effect 
other than issueing the same query back to back & hoping for good buffer
hits? 

	On another note, does anyone know what Oracle's SET TIMER command 
measures - i.e. does it include displays? It seems thay can issue this 
interactively & the impression is that it DOES include the displays, but I
am not convinced. 

Thanks
Janet