From: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
---|---|
To: | Hannu Krosing <hannu(at)tm(dot)ee> |
Cc: | Sergio Bruder <bruder(at)conectiva(dot)com(dot)br>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Any tips for this particular performance problem? |
Date: | 2001-07-10 14:54:54 |
Message-ID: | 200107101454.f6AEssk16767@jupiter.us.greatbridge.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hannu Krosing wrote:
> Sergio Bruder wrote:
> >
> > If you have time, take a quick look at
> >
> > http://acidlab.sourceforge.net/perf/acid_perf.html
> >
> > PostgreSQL has serious scalability problems with snort + acid. Any
> > advices?
>
> Usually porting from MySQL to PostgreSQL needs some rewrite of
> queries and process logic if good performance is required.
>
> > (Now I'm using MySQL with my SNORT/ACID setup, but I'm willing to
> > change to PostgreSQL if more tests are needed)
>
> Are these tests run using BSDDB backend (for transaction support) or
> the old/fast MySQL storage ?
I'm not familiar with SNORT/ACID, but I assume that the DB
schema and queries are basically all identically for all the
databases.
Well, how such analyzis software can be implemented without
views and stored procedures is a mystery to me, but at least
it must do a whole lot of PHP-aerobics.
I'd say as long as the database is used as a stupid data
container and not as a relational database management system,
just don't use Postgres. It's not designed to be stupid, so
it doesn't work well if used stupid.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2001-07-10 14:56:01 | Re: AW: pg_index.indislossy |
Previous Message | Peter Eisentraut | 2001-07-10 14:53:11 | Re: AW: pg_index.indislossy |