From: Rajesh Kumar Mallah <mallah@trade-india.com>
To: Rajesh Kumar Mallah <mallah@trade-india.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Suggestions for benchmarking 7.4RC2 against 7.3
Date: Wed, 12 Nov 2003 20:34:53 +0530
Message-ID: <3FB24C15.1020907@trade-india.com> (raw)
In-Reply-To: <3FB247FE.4080808@trade-india.com>
References: <3FB247FE.4080808@trade-india.com>
the error mentioned in first email has been overcome
by running osdb on the same machine hosting the DB server.
regds
mallah.
Rajesh Kumar Mallah wrote:
>
> Hi,
>
> I plan to put 7.4-RC2 in our production servers in next few hours.
>
> Since the hardware config & the performance related GUCs parameter
> are going to remain the same i am interested in seeing the performance
> improvements in 7.4 as compared 7.3 .
>
> For this i plan to use the OSDB 0.14 and compare the results for both
> the
> cases.
>
> Does any one has suggestions for comparing 7.4 against 7.3 ?
> Since i am using OSDB for second time only any tips/guidance
> on usage of that is also appreciated.
>
>
>
> H/W config:
>
> CPU: 4 X Intel(R) Xeon(TM) CPU 2.00GHz
> MEM : 2 GB
> I/O config : PGDATA on 10000 RPM Ultra160 scsi , pg_xlog on a similar
> seperate SCSI
>
> GUC:
> shared_buffers = 10000
> max_fsm_relations = 5000
> max_fsm_pages = 55099264
> sort_mem = 16384
> vacuum_mem = 8192
>
> All other performance related parameter have default
> value eg:
>
> #effective_cache_size = 1000 # typically 8KB each
> #random_page_cost = 4 # units are one sequential page fetch
> cost
> #cpu_tuple_cost = 0.01 # (same)
> #cpu_index_tuple_cost = 0.001 # (same)
> #cpu_operator_cost = 0.0025 # (same)
>
>
>
> BTW i get following error at the moment:
> -----------------------------------------
> /usr/local/bin/osdb-pg-ui --postgresql=no_hash_index
> "osdb"
> "Invoked: /usr/local/bin/osdb-pg-ui --postgresql=no_hash_index"
>
> create_tables() 0.78 seconds return value = 0
> load() 1.02 seconds return value = 0
> create_idx_uniques_key_bt() 0.64 seconds return value = 0
> create_idx_updates_key_bt() 0.61 seconds return value = 0
> create_idx_hundred_key_bt() 0.61 seconds return value = 0
> create_idx_tenpct_key_bt() 0.62 seconds return value = 0
> create_idx_tenpct_key_code_bt() 0.45 seconds return value = 0
> create_idx_tiny_key_bt() 0.46 seconds return value = 0
> create_idx_tenpct_int_bt() 0.46 seconds return value = 0
> create_idx_tenpct_signed_bt() 0.45 seconds return value = 0
> create_idx_uniques_code_h() 0.46 seconds return value = 0
> create_idx_tenpct_double_bt() 0.46 seconds return value = 0
> create_idx_updates_decim_bt() 0.45 seconds return value = 0
> create_idx_tenpct_float_bt() 0.46 seconds return value = 0
> create_idx_updates_int_bt() 0.46 seconds return value = 0
> create_idx_tenpct_decim_bt() 0.46 seconds return value = 0
> create_idx_hundred_code_h() 0.45 seconds return value = 0
> create_idx_tenpct_name_h() 0.46 seconds return value = 0
> create_idx_updates_code_h() 0.46 seconds return value = 0
> create_idx_tenpct_code_h() 0.45 seconds return value = 0
> create_idx_updates_double_bt() 0.46 seconds return value = 0
> create_idx_hundred_foreign() 0.41 seconds return value = 0
> populateDataBase() 11.54 seconds return value = 0
>
> Error in test Counting tuples at (6746)osdb.c:294:
> ... empty database -- empty results
> perror() reports: Resource temporarily unavailable
>
> someone sighup'd the parent
>
> Any clue?
>
> ------------------------------------------
>
>
> Regards
> Mallah.
>
>
>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: mallah@trade-india.com
Subject: Re: Suggestions for benchmarking 7.4RC2 against 7.3
In-Reply-To: <3FB24C15.1020907@trade-india.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox