Re: New boxes available for QA - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: New boxes available for QA
Date
Msg-id 20080401132903.GR4999@tamriel.snowman.net
Whole thread Raw
In response to New boxes available for QA  ("Guillaume Smet" <guillaume.smet@gmail.com>)
Responses Re: New boxes available for QA  ("Guillaume Smet" <guillaume.smet@gmail.com>)
List pgsql-hackers
Guillaume,

* Guillaume Smet (guillaume.smet@gmail.com) wrote:
> These servers are available 24/7 to PostgreSQL QA and won't be used
> for other purposes.

Awesome.

> Concerning the second point, I wonder if it's not worth it to have a
> very simple thing already reporting results as the development cycle
> for 8.4 has already started (perhaps several pgbench unit tests
> testing various type of queries with a daily tree). Thoughts?

It didn't occur to me before, but, if you've got a decent amount of disk
space and server time..

I'm almost done scripting up everything to load the TIGER/Line
Shapefiles from the US Census into PostgreSQL/PostGIS.  Once it's done
and working I would be happy to provide it to whomever asks, and it
might be an interesting data set to load/query and look at benchmarks
with.  There's alot of GIST index creation, as well as other indexes
like soundex(), and I'm planning to use partitioning of some sort for
the geocoder.  We could, for example, come up with some set of arbitrary
addresses to geocode and see what the performance of that is.

It's just a thought, and it's a large/"real" data set to play with.

The data set is 22G compressed shapefiles/dbf files.  Based on my
initial numers I think it'll grow to around 50G loaded into PostgreSQL
(I'll have better numbers later today).  You can get the files from
here: http://ftp2.census.gov/geo/tiger/TIGER2007FE/ Or, if you run into
a problem with that, I can provide a pretty fast site to pull them from
as well (15Mb/s).
Thanks,
    Stephen

pgsql-hackers by date:

Previous
From: Stuart Brooks
Date:
Subject: Re: [GENERAL] ANALYZE getting dead tuple count hopelessly wrong
Next
From: Mike Aubury
Date:
Subject: Scroll cursor oddity...