On Tue, 2005-08-16 at 10:46 -0700, Roger Hand wrote:
> The disks are ext3 with journalling type of ordered, but this was later
> changed to writeback with no apparent change in speed.
>
> They're on a Dell poweredge 6650 with LSI raid card, setup as follows:
> 4 disks raid 10 for indexes (145GB)
The system is a dual Xenon with 6Gig of ram and 14 73Gig 15K u320 scsi
drives. Plus 2 raid 1 system dives.
RedHat EL ES4 is the OS.
Any1 have any suggestions as to the configuration? The database is about
60 Gig's. Should jump to 120 here quite soon. Mus of the searches
involve people's names.
7.4 is the pg version BTWgoing to switch to 8 if it's worth it.
Ingrate, n.: A man who bites the hand that feeds him, and then complains
of indigestion.
--
"Don't say yes until I finish talking."
-- Darryl F. Zanuck
signature.asc
Description: This is a digitally signed mess
Summary
===
We are writing to the db pretty much 24 hours a day.
Recently the amount of data we write has increased, and the query speed,
formerly okay, has taken a dive.
The query is using the indexes as expected, so I don't _think_ I have a query
tuning issue, just an io problem.
The first
>
> One little thing. Did you shutdown sql2000 while testing
> postgresql? Remember that postgresql uses system cache.
> Sql2000 uses a large part of memory as buffer and it will not
> be available to operating system. I must say that, probably,
> results will be the same, but it will be a b
> Ulrich Wisser wrote:
> >
> > one of our services is click counting for on line advertising. We do
> > this by importing Apache log files every five minutes. This results in a
> > lot of insert and delete statements.
...
> If you are doing mostly inserting, make sure you are in a transaction,
We
> De : Magnus Hagander [mailto:[EMAIL PROTECTED]
> Out of curiosity, what plan do you get from SQLServer? I bet
> it's a clustered index scan...
>
>
> //Magnus
>
I have a Table scan and Hashaggregate...
Stephane
---(end of broadcast)---
TI
Barry,
I have made a similar experience, moving a big Oracle data base to
Postgres 8.03 on linux.
The first impact was similar, huge performance problems.
The main problem was bad planner choices. The cause in our case: bad
parameter types in the jdbc set methods (I guess you use Java). For
oracle
Mahesh Shinde wrote:
Hi
I am using Postgres version
**PostgreSQL 7.4.5 on i686-pc-linux-gnu, compiled by GCC gcc
(GCC) 3.2.2 20030222 (Red Hat Linux 3.2.2-5).* *
for an multy user desktop application using VB 6.0 as a front
end toll.
To connect To the PostgreSQL I am u
John Arbash Meinel wrote :
>
> You might also try a different query, something like:
>
> SELECT DISTINCT cod FROM mytable ORDER BY cod GROUP BY cod;
> (You may or may not want order by, or group by, try the different
> combinations.)
> It might be possible to have the planner realize that all y
On 18 Aug 2005, at 16:01, Sebastian Lallana wrote:
It exists something like this? Does anybody has experience about
this subject?
I've just been through this with a client with both a badly tuned Pg and
an application being less than optimal.
First, find a benchmark. Just something you can
At 01:55 PM 8/18/2005, John Arbash Meinel wrote:
Jeremiah Jahn wrote:
>here's an example standard query. Ireally have to make the first hit go
>faster. The table is clustered as well on full_name as well. 'Smith%'
>took 87 seconds on the first hit. I wonder if I set up may array wrong.
>I remebe
Christopher
> You could use a 1 column/1 row table perhaps. Use some sort of
locking
> mechanism.
>
> Also, check out contrib/userlock
userlock is definitely the way to go for this type of problem.
The are really the only way to provide locking facilities that live
outside transactions.
You
Jeremiah Jahn wrote:
>here's an example standard query. Ireally have to make the first hit go
>faster. The table is clustered as well on full_name as well. 'Smith%'
>took 87 seconds on the first hit. I wonder if I set up may array wrong.
>I remeber see something about DMA access versus something e
here's an example standard query. Ireally have to make the first hit go
faster. The table is clustered as well on full_name as well. 'Smith%'
took 87 seconds on the first hit. I wonder if I set up may array wrong.
I remeber see something about DMA access versus something else, and
choose DMA access
Jeremiah Jahn wrote:
>On Wed, 2005-08-17 at 21:21 -0500, John A Meinel wrote:
>
>
>>Jeremiah Jahn wrote:
>>
>>
>>>I just put together a system with 6GB of ram on a 14 disk raid 10 array.
>>>When I run my usual big painful queries, I get very little to know
>>>memory usage. My production box
Sebastian,
> We are having serious performance problems using JBOSS and PGSQL.
How about some information about your application? Performance tuning
approaches vary widely according to what you're doing with the database.
Also, read this:
http://www.powerpostgresql.com/PerfList
> I'm sure th
On Wed, 2005-08-17 at 21:21 -0500, John A Meinel wrote:
> Jeremiah Jahn wrote:
> > I just put together a system with 6GB of ram on a 14 disk raid 10 array.
> > When I run my usual big painful queries, I get very little to know
> > memory usage. My production box (raid 5 4GB ram) hovers at 3.9GB use
Hello:
We are having serious performance problems using
JBOSS and PGSQL.
I’m sure the problem has to do with the
application itself (and neither with JBOSS nor PGSQL) but the fact is that we are using desktop equipment
to run both Jboss and Postgresql (An Athlon 2600, 1
Gb Ram, IDE HDD wi
Qingqing Zhou wrote:
> "Alvaro Herrera" <[EMAIL PROTECTED]> writes
>
>>Interesting; do they use an overwriting storage manager like Oracle, or
>>a non-overwriting one like Postgres?
>>
>
>
> They call this MVCC "RLV(row level versioning)". I think they use rollback
> segment like Oracle (a.k.a "ver
On Aug 17, 2005, at 10:11 PM, Jeremiah Jahn wrote:
I just put together a system with 6GB of ram on a 14 disk raid 10
array.
When I run my usual big painful queries, I get very little to know
memory usage. My production box (raid 5 4GB ram) hovers at 3.9GB used
most of the time. the new devel
"Alvaro Herrera" <[EMAIL PROTECTED]> writes
>
> Interesting; do they use an overwriting storage manager like Oracle, or
> a non-overwriting one like Postgres?
>
They call this MVCC "RLV(row level versioning)". I think they use rollback
segment like Oracle (a.k.a "version store" or tempdb in SQL S
22 matches
Mail list logo