From: Rod Taylor <rbt@rbt.ca>
To: shridhar_daithankar@persistent.co.in
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: PostgreSQL vs. MySQL
Date: 04 Jul 2003 11:06:03 -0400
Message-ID: <1057331162.40425.79.camel@jester> (raw)
In-Reply-To: <3F05E144.10448.6784AB@localhost>
References: <20030704142800.GC4592@libertyrms.info>
<3F05E144.10448.6784AB@localhost>
> 2. Postgresql uses shared memory being process based architecture. Mysql uses
> process memory being threaded application. It does not need kernel settings to
> work and usually works best it can.
MySQL has other issues with the kernel due to their threading choice
such as memory limits per process, or poor threaded SMP support on some
platforms (inability for a single process to use more than one CPU at a
time regardless of thread count).
Threads aren't an easy way around kernel limitations, which is probably
why Apache has gone for a combination of the two -- but of course that
adds complexity.
Attachments:
signature.asc (application/pgp-signature, 186B) download
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-docs@postgresql.org
Cc: rbt@rbt.ca, shridhar_daithankar@persistent.co.in, pgsql-performance@postgresql.org
Subject: Re: PostgreSQL vs. MySQL
In-Reply-To: <1057331162.40425.79.camel@jester>
* 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