REVMEDIA FKB Articles - AREV, OI, REV G, jREV, JCDC, LIVEWATER,ADVANCED REVELATION, OPENINSIGHT, REVELATION G

RevMedia FKB

Document	V3I9A4
Title	VROOM - Doubling MFS Write Speed
Keywords	MFS BFS SI.MFS SPEED %%SI%% VROOM
Text	When developing MFSs it is frequently necessary to check whether the record being written has changed since it was read FROM disk Traditionally this is done by saving off the appropriate VARIABLES CHANGING the BFS code to Read from Write and performing a DIRECT BFS call to access the old record Whilst this is effective it does mean that every file write needs to generate a corresponding file read thus doubling file i/o Developers who have taken the time to examine the !! source code generated for the ! routines will notice comments relating to the CACHING of records by the filing system such as IF OLD FLAG THEN * If something cached then ID and FILEVAR must match IF OLD ID EQ @ID THEN IF OLD FV EQ FILEVAR THEN When a record is read FROM disk SI MFS caches it in the LABELLED common area %%SI%% in the variable OLD REC The documented structure of %%SI%% is as follows COMMON /%%SI%%/ A B C D OLD REC OLD FLAG OLD FV OLD ID I J L If OLD FLAG is set to 0 then OLD REC does not contain a record for some reason (possibly read failure) If it is set to 1 then OLD REC does contain a record but if set to 2 it does not contain a record as the record read from disk was new To avoid the second read at the MFS level it would therefore be possible to check the OLD FLAG if this check is passed to compare the old id to the current id then the old filevar to the CURRENT filevar and if all conditions pass avoid making the extra read and just compare the values in OLD REC (Volume 3 Issue 9 Page 5)

[revmedia/copyrigh.htm]

Page last modified: 08/02/03