Scribd
Upload
74 views

Lesson 7 INF211 Lect 08

This document provides an overview of organizing files for performance. It discusses strategies for record deletion, including marking deleted records and compacting files later. Available space from deleted records can be reused by maintaining an available list. When adding records, different placement strategies like best-fit and worst-fit can be used. The document also covers sorting file records by key to enable faster binary searching compared to sequential searching. An index file can be created by sorting just the keys in memory and writing the file back in sorted order.

Uploaded by

Russel Ponferrada
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
74 views

Lesson 7 INF211 Lect 08

This document provides an overview of organizing files for performance. It discusses strategies for record deletion, including marking deleted records and compacting files later. Available space from deleted records can be reused by maintaining an available list. When adding records, different placement strategies like best-fit and worst-fit can be used. The document also covers sorting file records by key to enable faster binary searching compared to sequential searching. An index file can be created by sorting just the keys in memory and writing the file back in sorted order.

Uploaded by

Russel Ponferrada
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 29

Lecture 8

Organizing Files for Performance

Previous
Previous Lecture
Lecture

Lecture 7

Data Compression

Data Compression: how to

make files smaller

Today
Today Lecture
Lecture

Overview
In this lecture, we continue to

focus on file organization, but


with a different motivation.
This time we look at ways to
organize or re-organize files in
order to improve performance.

Outline

Reclaiming Space in Files


Sorting and Binary Searching

Part 1

Motivation
Let us consider a file of records (fixed length

or variable length).
We know how to create a file, add records to
a file and modify the content of a record.
These actions can be performed physically by using

the various basic file operations we have seen

open a file for writing or appending, going to a position


of a file using "seek" and writing the new information
there.

What happens if records need to be deleted?


There is no basic operation that allows us to

"remove part of a file".


Record deletion should be taken care by the
program responsible for file organization.

Strategies for Record


How to delete records and reuse the unused space?
Deletion
1. Record Deletion and Storage

Compaction

Deletion can be done by "marking" a record as


deleted.

Place "*" at the beginning of the record; or


Have a special field that indicates one of two states:
"deleted" or "not deleted"

Note that the space for the record is not


released, but the program that manipulates
the file must include logic that checks if record
is deleted or not.
After a lot of records have been deleted a
special program is used to squeeze the file

this is called Storage Compaction.

Strategies for Record


Deletion
2. Deleting Fixed-Length Records and

Reclaiming Space Dynamically


How to use the space of deleted records
for storing records that are added later?
Use an "AVAIL LIST", a linked list of
available records.

a header record (at the beginning of the file)

stores the beginning of the AVAIL LIST (-1 can


represent the null pointer)
when a record is deleted, it is marked as
deleted and inserted into the AVAIL LIST. The
record space is in the same position as before,
but it is logically placed into AVAIL LIST.

Strategies for Record


Deletion

Strategies for Record


Deletion
3. Deleting Variable-Length

Records
Use an AVAIL LIST as before but take
care of the variable-length
difficulties.
The records in AVAIL LIST must store
its size as a field.
RRN can not be used, but exact byte
offset must be used.

Strategies for Record


Deletion

Addition of records must find a large

enough record in AVAIL LIST.

Placement Strategies for


New Records
There are several strategies for selecting a record from
AVAIL LIST when adding a new record

Placement Strategies for


New Records

Placement Strategies for


New Records

Placement Strategies for


New Records
When choosing between strategies we must

consider two types of fragmentation within a file


Internal Fragmentation: wasted space within a
record.
External Fragmentation: space is available at
AVAIL LIST, but it is so small that cannot be reused.
For each of the following approaches, which type
of fragmentation arises, and which placement
strategy is more suitable?
When the added record is smaller than the item
taken from AVAIL LIST
leave the space unused within the record
return the unused space as a new available record to

AVAIL LIST

External Fragmentation
Ways of combating external fragmentation
Coalescing the holes: if two records in
AVAIL LIST are adjacent, combine them
into a larger record.
Minimize fragmentation by using one of
the previously mentioned placement
strategies
for example: worst-fit strategy is better than

best-fit strategy in terms of external


fragmentation when unused space is returned
to AVAIL LIST.

Part 2

Binary Searching
Let us consider fixed-length records that must

be searched by a key value.


If we knew the RRN of the record identified by
this key value, we could jump directly to the
record (using "seek").
In practice, we do not have this information
and we must search for the record containing
this key value.
If the file is not sorted by the key value we
may have to look at every possible record
before we find the desired record.
An alternative to this is to maintain the file
sorted by key value and use binary searching.

A
Al Bin
go ar
rit y S
hm ea
in rch
C+
+

Binary Search versus


Sequential Search
Binary Search: O(log2n)
Sequential Search: O(n)
If the file size is doubled,
sequential search time is doubled, while
binary search time increases by 1.

Keysorting
Suppose a file needs to be sorted, but

it is too big to fit into main memory.


To sort the file, we only need the keys,
Suppose that all the keys fit into main
memory.
Idea
Bring the keys to main memory plus

corresponding RRN
Do internal sorting of keys
Rewrite the file in sorted order

Example

Indexing
How much effort we must do (in

terms of disk accesses)?


Read file sequentially once
Go through each record in random order

(seek)
Write each record once (sequentially)

Why bother to write the file back?


Use keynode array to create an index file

instead

Pinned Records
Remember that in order to support

deletions we used AVAIL LIST a list of


available records
The AVAIL LIST contains info on the
physical information of records
Such record is said to be pinned
If we use an index file for sorting
the AVAIL LIST and positions of
records remain unchanged

Next
Next Lecture
Lecture

Indexing

Reclaiming space in files


Sorting and Binary Searching

Questions?

You might also like