[seanc@FreeBSD.org: Re: cvs commit: ports/databases/postgresql-devel Makefile distinfo pkg-message pkg-plist]

From: Sean Chittenden (seanc_at_FreeBSD.org)
Date: 10/01/03

  • Next message: S H A N: "How to do calculations for performance tuning?"
    Date: Wed, 1 Oct 2003 00:46:25 -0700
    To: database@FreeBSD.org
    
    
    

    FWIW, I just updated postgresql-devel to the latest snapshot and as
    promised, I added the _ability_ to change postgresql-devel's block
    sizes to 16K or 32K. The default block size still remains at 8K.

    If you have hardware and testing time to burn, I'd be interested in
    anyone's results if someone decides to perform any kind of
    benchmarking with differing block sizes. Some have found the bigger
    block sizes to speed up some types of work loads anywhere from 10-25%,
    others have found no difference. Any data that people have on this
    would be of interest to me and I would greatly appreciate hearing
    about anyones results. Info that's helpful include what version
    FreeBSD, file system info, UFS block sizes as well as PG block sizes,
    and basic info about your app that you used to test (50/50 read
    writes, 40/60, etc).

    Please note that changing block sizes should be done with care and
    will result in the need to dump/initdb/reload, and adjustment of
    postgresql.conf values (ex: effective_cache_size) that depend on 8K
    block sizes. Playing with PG's block sizes will create
    incompatibilities between databases/postgresql-devel and
    databases/postgresql7 if the block sizes differ. You have been
    warned.

    If you have any questions about this, please take up such discussions
    on the database@ list. -sc

    PS Valid values for WITH_PGBLOCKSIZE are "16K" or "32K"

    -- 
    Sean Chittenden
    
    

    attached mail follows:


    Date: Wed, 1 Oct 2003 00:26:31 -0700
    To: ports-committers@FreeBSD.org, cvs-ports@FreeBSD.org, cvs-all@FreeBSD.org
    
    

    > seanc 2003/10/01 00:21:41 PDT
    >
    > FreeBSD ports repository
    >
    > Modified files:
    > databases/postgresql-devel Makefile distinfo pkg-message
    > pkg-plist
    > Log:
    > Update to the latest snapshot for 7.4beta3. Mostly bug fixes, but the
    > most significant change is the ability to change PostgreSQL's block size
    > with the nob: WITH_PGBLOCKSIZE=("16K"|"32K"). Release notes:
    >
    > http://developer.postgresql.org/docs/postgres/release.html#RELEASE-DEVEL

    For those with hardware and testing time to burn, I'm particularly
    interested in knowing if someone notices one of these sizes performs
    better form them or not. Some have found the bigger block sizes to
    speed up some types of work loads anywhere from 10-25%, others have
    found no difference. Any data that people have on this would be of
    interest to me and I would greatly appreciate hearing about anyones
    results. Please note that changing block sizes should be done with
    care and will result in the need to dump/initdb/reload and can create
    incompatibilities between databases/postgresql-devel and
    databases/postgresql7.

    -sc

    -- 
    Sean Chittenden
    
    

    _______________________________________________
    freebsd-performance@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-performance
    To unsubscribe, send any mail to "freebsd-performance-unsubscribe@freebsd.org"


  • Next message: S H A N: "How to do calculations for performance tuning?"