Thanks,
I had tried these with little improvement. After looking at pgbench.c
and reading other comments my conclusion is that postgres is this slow on
doing inserts. The fast means of inserts a lot of data is to use COPY which
is not useful for creating beans.
It looks like my best bet is to ether switch to HSQL or at least
use a combination of Postgres and HSQL.
> -----Original Message-----
> From: Sach Jobb [SMTP:[EMAIL PROTECTED]]
> Sent: Sunday, January 28, 2001 1:42 PM
> To: Orion-Interest
> Subject: Re: Postgress Performance
>
> It could be a performance issue with Postgres. By default Postgres uses a
> "paranoid" setting that writes each transaction to disk immediately after
> the transaction is completed. This is done to protect the integrity of the
> database, as at anytime the database could go down and data could be
> lost.
>
> However, when dealing with large numbers of transaction this can severely
> impair performance. So, you can disable it by changing your postmaster
> line to something like this:
>
> postmaster -o -F -D /mypath/to/datadir
>
> You can also get a little speed out of detaching from the tty you started
> it from by using the "-S" switch.
>
> And, of course, in terms of performance when deploying you should really
> tweak the number of backend connections.
>
> Hope that helps.
>
>
> thanks,
> sach
>
> %s/windows/linux/g
>
>
> On Sun, 28 Jan 2001, Paul Fink wrote:
>
> > In general Orion and postgres seem to work well together
> > but I have a problem with the performance of inserts.
> >
> > As the size of the table increases the rate at which I can do
> > inserts, or bean creates, decreases dramatically.
> >
> > I have a very simple Alarm entity bean with a single Long
> > as the primary key. Running under Linux on a PIII. When
> > I start with an empty table I can create new Alarm beans
> > at a rate of about 40/sec. When the table reaches 10K entries
> > the rate is down to 10/sec and continues to drop.
> >
> > I have the entity bean wrapped by a session bean and I do
> > several creates per transaction. The only trick I've found for
> > speeding up postgress is the "-o -F" flag which I've done.
> >
> >
> >
>
