From: JanWieck@t-online.de
To: Nikolaj Lundsgaard <Nikolaj@konfus.dk>
Cc: pgsql-sql@postgresql.org
Subject: Re: Benchmark
Date: Fri, 2 Jun 2000 22:58:23 +0200 (MEST)
Message-ID: <200006022058.WAA07767@hot.jw.home> (raw)
In-Reply-To: <000b01bfccc1$53ef2840$8fd426c0@commando.kampsax.dtu.dk>
Nikolaj Lundsgaard wrote:
> Is there anywhere I can find some benchmark test for postgres. The reason is that I want to use it for a site that could have several simultanous users querying the database and I want to be sure that it is stable (and fast) enough to handle that kind of (ab)use.
There is actually no (DB-independant) benchmark suite
publicly available.
>
> Also which is fastest ?
>
> 1. A query (using index of course) for a text in the database.
>
> or
>
> 2. Reading from a file on the harddisk.
>
>
> If the answer is 1 will the answer still be 1 if I do it several times (100.000+ a day)
Since any DB access boils down somehow to file access, it
could never be 1 (as long as your solution doesn't need to
sequentially read big files to find small pieces of
information).
The question you have to ask is, what would happen in a
concurrent environment? If there's at least one writing
process, must the entire information be blocked from reading?
Postgres uses MVCC (Multi Version Concurrency Control) for
it. So no reader will ever be blocked by a writer - it simply
sees a snapshot of the entire data as it was when he executed
the first DML statement.
If you have total static data, that never changes during
uptime of your application, use flat files or some higher
level file interface like GDB or MySQL.
If you have data in motion, use a database.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck@Yahoo.com #
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: JanWieck@t-online.de, Nikolaj@konfus.dk
Subject: Re: Benchmark
In-Reply-To: <200006022058.WAA07767@hot.jw.home>
References: <000b01bfccc1$53ef2840$8fd426c0@commando.kampsax.dtu.dk> <200006022058.WAA07767@hot.jw.home>
* 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