dbTalk Databases Forums  

Database Application with A LOT OF records

comp.databases comp.databases


Discuss Database Application with A LOT OF records in the comp.databases forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
dominik.businger@gmail.com
 
Posts: n/a

Default Database Application with A LOT OF records - 10-08-2006 , 04:47 PM






Hi all,

I'm trying to do some estimations for an application we're about to
build. And I'm not quite sure if the numbers of records we're facing
can be handeled at all.

We've got 3 critical tables with really a lot of records to be
stored... The tables are fairly simple with between 3 to 10 columns but
our calculations gave that

Table 1 has to store 96 billion records of arround 60bytes each,
Table 2 has to store 1.2 billion records of arround 150 bytes each and
Table 3 has to store 32 billion records of arround 32 bytes each.

This all summs up to arround 7 TeraBytes of data without any indices
counted yet. We guess that from the moment the application is
operational there will be an average of 350 insert and 150 update
statements (transactions) per second.

Can this kind of dataload be handeled by todays database servers?
Will the amount of insert and update transactions be possible? Or are
we way out of scale?
Is this allready in a dimension where clustering is needed? Or can this
still be done by a single machine?

Thanx a lof for you answers in advance!
Dom.


Reply With Quote
  #2  
Old   
Jim Kennedy
 
Posts: n/a

Default Re: Database Application with A LOT OF records - 10-08-2006 , 07:33 PM







<dominik.businger (AT) gmail (DOT) com> wrote

Quote:
Hi all,

I'm trying to do some estimations for an application we're about to
build. And I'm not quite sure if the numbers of records we're facing
can be handeled at all.

We've got 3 critical tables with really a lot of records to be
stored... The tables are fairly simple with between 3 to 10 columns but
our calculations gave that

Table 1 has to store 96 billion records of arround 60bytes each,
Table 2 has to store 1.2 billion records of arround 150 bytes each and
Table 3 has to store 32 billion records of arround 32 bytes each.

This all summs up to arround 7 TeraBytes of data without any indices
counted yet. We guess that from the moment the application is
operational there will be an average of 350 insert and 150 update
statements (transactions) per second.

Can this kind of dataload be handeled by todays database servers?
Will the amount of insert and update transactions be possible? Or are
we way out of scale?
Is this allready in a dimension where clustering is needed? Or can this
still be done by a single machine?

Thanx a lof for you answers in advance!
Dom.

Yes, there are vendor's that can handle that volume. Call the major vendors
and ask them for customer references for customer's doing similar volumes.
Jim




Reply With Quote
  #3  
Old   
toby
 
Posts: n/a

Default Re: Database Application with A LOT OF records - 10-11-2006 , 05:39 AM




dominik.businger (AT) gmail (DOT) com wrote:
Quote:
Hi all,

I'm trying to do some estimations for an application we're about to
build. ...
Table 1 has to store 96 billion records of arround 60bytes each,
Table 2 has to store 1.2 billion records of arround 150 bytes each and
Table 3 has to store 32 billion records of arround 32 bytes each.

This all summs up to arround 7 TeraBytes of data without any indices
counted yet. We guess that from the moment the application is
operational there will be an average of 350 insert and 150 update
statements (transactions) per second.

Can this kind of dataload be handeled by todays database servers?
If you want access via SQL, MySQL can adapt to this type of application
readily with its pluggable storage engine. Some case studies address
this type of application:
http://mysql.com/why-mysql/case-studies/
In particular, see "Fortum Relies on MySQL to Monitor Power Plant in
Real Time" (about 2/3rds down).
\\
UPSYS calculated that the amount of data simultaneously
stored would eventually grow to 30 Terabytes of data. Very
expensive hardware would have been required to meet performance
demands if this amount of data was stored in a conventional
storage engine. Using the flexibility of the MySQL
pluggable storage engine architecture, the decision was made
to create a new, more compact table handler, specifically
tailored to the needs of the project.
//
Contact a MySQL representative in your area for more info, I've found
them very helpful; they also offer flexible and responsive support.

Quote:
Will the amount of insert and update transactions be possible? Or are
we way out of scale?
Is this allready in a dimension where clustering is needed? Or can this
still be done by a single machine?

Thanx a lof for you answers in advance!
Dom.


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.