DB BLOCK SIZE in Banking Applications
DBAsupport.com Forums - Powered by vBulletin
Page 1 of 3 123 LastLast
Results 1 to 10 of 24

Thread: DB BLOCK SIZE in Banking Applications

  1. #1
    Join Date
    Nov 2000
    Posts
    101
    Hi All,

    DB: Oracle9i on IBM-AIX 4.3.

    I am designing a database, my DB is going to be used in Banking purpose, typical Banking applications like FOREX,LD,LC,CREDIT CARDS will be used in the DB.

    What could be best size of DB_BLOCK_SIZE ?


    Thanks in Advance,

    gandhi
    OCP-DBA.

  2. #2
    Join Date
    Mar 2002
    Posts
    301
    Hi,

    8k should be fine.

    Vijay.
    Say No To Plastics

  3. #3
    Join Date
    Apr 2001
    Location
    Bangalore, India
    Posts
    727
    Hi

    Vijay is absolutely correct... I am working in Banking DB.. Our setup is with also 8KB. Banking is really with OLTP..

    Regards
    Thomas Saviour(royxavier@yahoo.com)
    Technical Lead (Databases)
    Thomson Reuters (Markets)

    http://ora600tom.wordpress.com/

  4. #4
    Join Date
    May 2000
    Location
    ATLANTA, GA, USA
    Posts
    3,135
    32 K is the right choice.

  5. #5
    Join Date
    Jun 2000
    Location
    Madrid, Spain
    Posts
    7,447
    wont 32K waste you data block buffer too much?

  6. #6
    Join Date
    Nov 2000
    Location
    greenwich.ct.us
    Posts
    9,092
    It doesn't really matter in 9i. You can have multiple block sizes.
    Jeff Hunter
    marist89@yahoo.com
    http://marist89.blogspot.com/
    Get Firefox!
    "I pledge to stop eating sharks fin soup and will not do so under any circumstances."

  7. #7
    Join Date
    Mar 2002
    Posts
    534
    I think that 32k is too much for an OLTP system. The reason for this is that you would waste space in the buffer cache. For random access to data, like in an OLP system, I would recommand a smaller block size like 8k.

    It's correct that you can have multiple block sizes in Oracle9i but the block size for the keep buffer pool and recycle buffer pool can only be defined for the default block size.

  8. #8
    Join Date
    Dec 2000
    Location
    Ljubljana, Slovenia
    Posts
    4,439
    You can find pros and cons for everything. You mentioned wasting space in buffer cache with 32K block size. But at the same time we are talking about banking application where speed is of the primary concern. Well, I don't think any bank will have a problem investing few hundred or thousand $ in buying enough RAM if it realy wants fast responces from its database. And 32K blocks realy can improve performance compared to 8K because of much less I/O. Data is much more tightly packed in table blocks, and what is even more important - indexes will be much "flatter" with 32K, resulting in saving I/O with each and every query in OLTP system.

    Bottom line: I don't find "wasting space in buffer cache" to be a realy valid argument against using larger block sizes. Simply invest few bucks and have larger buffer cache, and the problem is gone. But reducing I/O is a valid argument in favor of using larger block size. Larger blocks simply mean fewer I/O, particulary in OLTP where practicaly everything is accessed via indexes.
    Jurij Modic
    ASCII a stupid question, get a stupid ANSI
    24 hours in a day .... 24 beer in a case .... coincidence?

  9. #9
    Join Date
    Apr 2002
    Posts
    2

    32K blocks

    I do agree with jurij.Even oracle recommends a large block size be it an oltp or an olap database.

  10. #10
    Join Date
    Oct 2000
    Posts
    139
    not agreed

    in oltp small amount of rows are fetched, if let's sayin a query has to returns 10 rows in 10 blocks then instead of 80K Oracle have to read 320K into memory

    Has anyone benchmark this? Or this just theory you peeps are talking about?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Click Here to Expand Forum to Full Width