VERBatim - V77
Batch.Indexing
QTIPS - Batch.Indexing Close Down
What's New (and un(der)documented!) In 2.12
Bugs and PCs - Indexing 01 vs 1
VERBatim - V77
Index Sub Revisited
Indexing on Xlates
Advanced Revelation Initialisation Sequence (Overview) by Mike Pope
Simple Security
Batch.Indexing
QTIPS - Batch.Indexing Close Down
What's New (and un(der)documented!) In 2.12
RTP Series - RTP50
@ATTACK - @Messages
Advanced Revelation Initialisation Sequence (Overview) by Mike Pope
Caching in on the Frames Array - Mike Pope
Vroom
Vroom - Window Processing
Reader's Forum
VROOM - Doubling MFS Write Speed
QTIPS - DOS File Names
DOS Interfacing (Part II)
VERBatim - V116
@ATTACK - @Pri.File
@ATTACK - @Rollout.File
File Variables
How Indexes Are Updated
Index Record Layouts
QTIPS - File Variable of File In SELECT Statement
QTIPS - Amending non-Attached Files
LINEAR HASH FILE STRUCTURES - Part 1
Index Flush
QTIPS - File Handle Structure
VERBatim - V126
Esc.To.Exit
Uncommon Knowledge - WC_WST_CHAR%
QTIPS - DOSTime
VERBatim - V11
@ATTACK - @Backgrnd.Time
@ATTACK - @Index.Time
QTIPS - Time-outs in Windows
QTIPS - Improving the LH_VERIFY Window
@ATTACK - @Modal
Utility Diskette # 4
What's New (and un(der)documented!) In 2.12
Playing with Scan Codes
QTIPS - Compiling Protection Code
QTIPS - Invalid Code and Command
QTIPS - Code/Command Help
Compiling 64K on a Shoestring by Blaise Wrenn (LexStat Systems Ltd)
RTP Series - RTP38
VERBatim - V124
Rebuilding Indexes
QTIPS - Make.Index 2.11+
Index Flush
Caching in on the Frames Array - Mike Pope
Flashing Background
Background Processing
Creating Your Own Background Processes

RevMedia FKB

DocumentV3I9A5
TitleBatch.Indexing
KeywordsBATCH.INDEXING
TextBATCH INDEXING is a routine which permits the buffering of index
transactions in memory until certain pre set limits are reached USING this
routine speed improvements of 30%+ are typical The usage is simple just
call

BATCH INDEXING(1 File_Var) to turn batching on and
BATCH INDEXING(0 File_Var) to turn it off

From thereon index transactions are buffered in memory for that file and
not actually written to the ! datafile The pre set limits are documented in
the latest "System Subroutines" book FROM Revelation Technologies as follows

"BATCH INDEXING either BUFFERS a set amount of data (1 000 bytes) or buffers
for a limited time (5 seconds) whichever occurs first so you need not be
concerned WITH overrunning memory space"

Caveats
The information buffered by BATCH INDEXING is only flushed to disk by the !
code and by a DIRECT call to BATCH INDEXING turning the buffering off
Further only one file is buffered at a time This has four major
implications ;

You should NEVER logoff without first turning BATCH INDEXING off If
you do any buffered transactions will be lost (Fixed in 2 12)

The time between flushes is only 5 seconds if records are continually
being written to disk through the ! code That is if a record is
written to disk and then the machine is left standing for 24 hours the
buffered TRANSACTION will still be in memory However the moment a
record is written to the same file the record will be flushed

Neither INDEX FLUSH nor background indexing flush the buffered
transactions to disk regardless of the "Delay before indexing"
settings

If BATCH INDEXING is started on one file and transactions are buffered
and then BATCH INDEXING is started on a new file the old transactions
will be written to the new file


(Volume 3 Issue 9 Pages 5 6)
[revmedia/copyrigh.htm]

Page last modified: 31/01/03