dbTalk Databases Forums  

sequential disk read speed

comp.databases.theory comp.databases.theory


Discuss sequential disk read speed in the comp.databases.theory forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Darren
 
Posts: n/a

Default sequential disk read speed - 08-20-2008 , 07:36 PM






I am learning about database systems, and I am reading a book called
"Physical Database Design".

It gets to a bit about a large sequential access (e.g. for a full
table scan), and does the following:

It says "Since most disk systems use prefetch buffers to speed up
table scans, we
assume a 64 KB prefetch block"

So to calculate the time for a full table scan, it multiples the
number of 64KB blocks by the time it takes to seek and read (2.02ms).
In other words, it is seeking each 64KB block.

Why can a disk only read 64KB at a time? Is this a valid assumption?
Is this a disk limitation or a file system limitation?

Thanks




Reply With Quote
  #2  
Old   
Bob Badour
 
Posts: n/a

Default Re: sequential disk read speed - 08-20-2008 , 08:48 PM






Darren wrote:

Quote:
I am learning about database systems, and I am reading a book called
"Physical Database Design".

It gets to a bit about a large sequential access (e.g. for a full
table scan), and does the following:

It says "Since most disk systems use prefetch buffers to speed up
table scans, we
assume a 64 KB prefetch block"

So to calculate the time for a full table scan, it multiples the
number of 64KB blocks by the time it takes to seek and read (2.02ms).
In other words, it is seeking each 64KB block.

Why can a disk only read 64KB at a time? Is this a valid assumption?
Is this a disk limitation or a file system limitation?

Thanks
It's arbitrary. Some dbmses have a fixed block size; others allow one to
configure it as a parameter. Other systems try to read an entire track
or cylinder at a time. Whether the latter is feasible can change when
available cylinder sizes grow at different rates from available memory.

I suspect the book is giving a hypothetical just to demonstrate the
calculations involved.


Reply With Quote
  #3  
Old   
Bob Badour
 
Posts: n/a

Default Re: sequential disk read speed - 08-20-2008 , 08:48 PM



Darren wrote:

Quote:
I am learning about database systems, and I am reading a book called
"Physical Database Design".

It gets to a bit about a large sequential access (e.g. for a full
table scan), and does the following:

It says "Since most disk systems use prefetch buffers to speed up
table scans, we
assume a 64 KB prefetch block"

So to calculate the time for a full table scan, it multiples the
number of 64KB blocks by the time it takes to seek and read (2.02ms).
In other words, it is seeking each 64KB block.

Why can a disk only read 64KB at a time? Is this a valid assumption?
Is this a disk limitation or a file system limitation?

Thanks
It's arbitrary. Some dbmses have a fixed block size; others allow one to
configure it as a parameter. Other systems try to read an entire track
or cylinder at a time. Whether the latter is feasible can change when
available cylinder sizes grow at different rates from available memory.

I suspect the book is giving a hypothetical just to demonstrate the
calculations involved.


Reply With Quote
  #4  
Old   
Bob Badour
 
Posts: n/a

Default Re: sequential disk read speed - 08-20-2008 , 08:48 PM



Darren wrote:

Quote:
I am learning about database systems, and I am reading a book called
"Physical Database Design".

It gets to a bit about a large sequential access (e.g. for a full
table scan), and does the following:

It says "Since most disk systems use prefetch buffers to speed up
table scans, we
assume a 64 KB prefetch block"

So to calculate the time for a full table scan, it multiples the
number of 64KB blocks by the time it takes to seek and read (2.02ms).
In other words, it is seeking each 64KB block.

Why can a disk only read 64KB at a time? Is this a valid assumption?
Is this a disk limitation or a file system limitation?

Thanks
It's arbitrary. Some dbmses have a fixed block size; others allow one to
configure it as a parameter. Other systems try to read an entire track
or cylinder at a time. Whether the latter is feasible can change when
available cylinder sizes grow at different rates from available memory.

I suspect the book is giving a hypothetical just to demonstrate the
calculations involved.


Reply With Quote
  #5  
Old   
Bob Badour
 
Posts: n/a

Default Re: sequential disk read speed - 08-20-2008 , 08:48 PM



Darren wrote:

Quote:
I am learning about database systems, and I am reading a book called
"Physical Database Design".

It gets to a bit about a large sequential access (e.g. for a full
table scan), and does the following:

It says "Since most disk systems use prefetch buffers to speed up
table scans, we
assume a 64 KB prefetch block"

So to calculate the time for a full table scan, it multiples the
number of 64KB blocks by the time it takes to seek and read (2.02ms).
In other words, it is seeking each 64KB block.

Why can a disk only read 64KB at a time? Is this a valid assumption?
Is this a disk limitation or a file system limitation?

Thanks
It's arbitrary. Some dbmses have a fixed block size; others allow one to
configure it as a parameter. Other systems try to read an entire track
or cylinder at a time. Whether the latter is feasible can change when
available cylinder sizes grow at different rates from available memory.

I suspect the book is giving a hypothetical just to demonstrate the
calculations involved.


Reply With Quote
  #6  
Old   
Bob Badour
 
Posts: n/a

Default Re: sequential disk read speed - 08-20-2008 , 08:48 PM



Darren wrote:

Quote:
I am learning about database systems, and I am reading a book called
"Physical Database Design".

It gets to a bit about a large sequential access (e.g. for a full
table scan), and does the following:

It says "Since most disk systems use prefetch buffers to speed up
table scans, we
assume a 64 KB prefetch block"

So to calculate the time for a full table scan, it multiples the
number of 64KB blocks by the time it takes to seek and read (2.02ms).
In other words, it is seeking each 64KB block.

Why can a disk only read 64KB at a time? Is this a valid assumption?
Is this a disk limitation or a file system limitation?

Thanks
It's arbitrary. Some dbmses have a fixed block size; others allow one to
configure it as a parameter. Other systems try to read an entire track
or cylinder at a time. Whether the latter is feasible can change when
available cylinder sizes grow at different rates from available memory.

I suspect the book is giving a hypothetical just to demonstrate the
calculations involved.


Reply With Quote
  #7  
Old   
Bob Badour
 
Posts: n/a

Default Re: sequential disk read speed - 08-20-2008 , 08:48 PM



Darren wrote:

Quote:
I am learning about database systems, and I am reading a book called
"Physical Database Design".

It gets to a bit about a large sequential access (e.g. for a full
table scan), and does the following:

It says "Since most disk systems use prefetch buffers to speed up
table scans, we
assume a 64 KB prefetch block"

So to calculate the time for a full table scan, it multiples the
number of 64KB blocks by the time it takes to seek and read (2.02ms).
In other words, it is seeking each 64KB block.

Why can a disk only read 64KB at a time? Is this a valid assumption?
Is this a disk limitation or a file system limitation?

Thanks
It's arbitrary. Some dbmses have a fixed block size; others allow one to
configure it as a parameter. Other systems try to read an entire track
or cylinder at a time. Whether the latter is feasible can change when
available cylinder sizes grow at different rates from available memory.

I suspect the book is giving a hypothetical just to demonstrate the
calculations involved.


Reply With Quote
  #8  
Old   
Bob Badour
 
Posts: n/a

Default Re: sequential disk read speed - 08-20-2008 , 08:48 PM



Darren wrote:

Quote:
I am learning about database systems, and I am reading a book called
"Physical Database Design".

It gets to a bit about a large sequential access (e.g. for a full
table scan), and does the following:

It says "Since most disk systems use prefetch buffers to speed up
table scans, we
assume a 64 KB prefetch block"

So to calculate the time for a full table scan, it multiples the
number of 64KB blocks by the time it takes to seek and read (2.02ms).
In other words, it is seeking each 64KB block.

Why can a disk only read 64KB at a time? Is this a valid assumption?
Is this a disk limitation or a file system limitation?

Thanks
It's arbitrary. Some dbmses have a fixed block size; others allow one to
configure it as a parameter. Other systems try to read an entire track
or cylinder at a time. Whether the latter is feasible can change when
available cylinder sizes grow at different rates from available memory.

I suspect the book is giving a hypothetical just to demonstrate the
calculations involved.


Reply With Quote
  #9  
Old   
Bob Badour
 
Posts: n/a

Default Re: sequential disk read speed - 08-20-2008 , 08:48 PM



Darren wrote:

Quote:
I am learning about database systems, and I am reading a book called
"Physical Database Design".

It gets to a bit about a large sequential access (e.g. for a full
table scan), and does the following:

It says "Since most disk systems use prefetch buffers to speed up
table scans, we
assume a 64 KB prefetch block"

So to calculate the time for a full table scan, it multiples the
number of 64KB blocks by the time it takes to seek and read (2.02ms).
In other words, it is seeking each 64KB block.

Why can a disk only read 64KB at a time? Is this a valid assumption?
Is this a disk limitation or a file system limitation?

Thanks
It's arbitrary. Some dbmses have a fixed block size; others allow one to
configure it as a parameter. Other systems try to read an entire track
or cylinder at a time. Whether the latter is feasible can change when
available cylinder sizes grow at different rates from available memory.

I suspect the book is giving a hypothetical just to demonstrate the
calculations involved.


Reply With Quote
  #10  
Old   
Bob Badour
 
Posts: n/a

Default Re: sequential disk read speed - 08-20-2008 , 08:48 PM



Darren wrote:

Quote:
I am learning about database systems, and I am reading a book called
"Physical Database Design".

It gets to a bit about a large sequential access (e.g. for a full
table scan), and does the following:

It says "Since most disk systems use prefetch buffers to speed up
table scans, we
assume a 64 KB prefetch block"

So to calculate the time for a full table scan, it multiples the
number of 64KB blocks by the time it takes to seek and read (2.02ms).
In other words, it is seeking each 64KB block.

Why can a disk only read 64KB at a time? Is this a valid assumption?
Is this a disk limitation or a file system limitation?

Thanks
It's arbitrary. Some dbmses have a fixed block size; others allow one to
configure it as a parameter. Other systems try to read an entire track
or cylinder at a time. Whether the latter is feasible can change when
available cylinder sizes grow at different rates from available memory.

I suspect the book is giving a hypothetical just to demonstrate the
calculations involved.


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.