pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feedSwapping in 7.4.3
5+ messages / 4 participants
[nested] [flat]
* Swapping in 7.4.3
@ 2004-07-12 16:59 Jim Ewert <jim.ewert@excite.com>
0 siblings, 1 reply; 5+ messages in thread
From: Jim Ewert @ 2004-07-12 16:59 UTC (permalink / raw)
To: pgsql-performance
When I went to 7.4.3 (Slackware 9.1) w/ JDBC, the improvements are that it doesn't initially take much memory (have 512M) and didn't swap. I ran a full vaccum and a cluster before installation, however speed degaded to 1 *second* / update of one row in 150 rows of data, within a day! pg_autovacuum now gives excellent performance however it is taking 66M of swap; only 270k cached.
_______________________________________________
Join Excite! - http://www.excite.com
The most personalized portal on the Web!
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Swapping in 7.4.3
@ 2004-07-13 20:26 Matthew T. O'Connor <matthew@zeut.net>
parent: Jim Ewert <jim.ewert@excite.com>
0 siblings, 0 replies; 5+ messages in thread
From: Matthew T. O'Connor @ 2004-07-13 20:26 UTC (permalink / raw)
To: jim.ewert@excite.com; +Cc: pgsql-performance
Jim Ewert wrote:
> When I went to 7.4.3 (Slackware 9.1) w/ JDBC, the improvements are that it doesn't initially take much memory (have 512M) and didn't swap. I ran a full vaccum and a cluster before installation, however speed degaded to 1 *second* / update of one row in 150 rows of data, within a day! pg_autovacuum now gives excellent performance however it is taking 66M of swap; only 270k cached.
>
Are you saying that your system stays fast now that you are using
pg_autovacuum, but pg_autovacuum is using 66M of memory? Please
clarify, I'm not sure what question you want an answered.
Matthew
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Swapping in 7.4.3
@ 2004-07-15 13:49 Jim Ewert <jim.ewert@excite.com>
0 siblings, 1 reply; 5+ messages in thread
From: Jim Ewert @ 2004-07-15 13:49 UTC (permalink / raw)
To: matthew@zeut.net; +Cc: pgsql-performance
With pg_autovaccum it's now at 95M swap; averaging 5MB / day increase with same load. Cache slightly increases or decreases according to top.
--- On Tue 07/13, Matthew T. O'Connor < matthew@zeut.net > wrote:
From: Matthew T. O'Connor [mailto: matthew@zeut.net]
To: jim.ewert@excite.com
Cc: pgsql-performance@postgresql.org
Date: Tue, 13 Jul 2004 16:26:09 -0400
Subject: Re: [PERFORM] Swapping in 7.4.3
Jim Ewert wrote:<br>> When I went to 7.4.3 (Slackware 9.1) w/ JDBC, the improvements are that it doesn't initially take much memory (have 512M) and didn't swap. I ran a full vaccum and a cluster before installation, however speed degaded to 1 *second* / update of one row in 150 rows of data, within a day! pg_autovacuum now gives excellent performance however it is taking 66M of swap; only 270k cached.<br>> <br><br>Are you saying that your system stays fast now that you are using <br>pg_autovacuum, but pg_autovacuum is using 66M of memory? Please <br>clarify, I'm not sure what question you want an answered.<br><br>Matthew<br><br>
_______________________________________________
Join Excite! - http://www.excite.com
The most personalized portal on the Web!
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Swapping in 7.4.3
@ 2004-07-15 16:20 Scott Marlowe <smarlowe@qwest.net>
parent: Jim Ewert <jim.ewert@excite.com>
0 siblings, 1 reply; 5+ messages in thread
From: Scott Marlowe @ 2004-07-15 16:20 UTC (permalink / raw)
To: jim.ewert@excite.com; +Cc: matthew@zeut.net; pgsql-performance
This is normal. My personal workstation has been up for 16 days, and it
shows 65 megs used for swap. The linux kernel looks for things that
haven't been accessed in quite a while and tosses them into swap to free
up the memory for other uses.
This isn't PostgreSQL's fault, or anything elses. It's how a typical
Unix kernel works. I.e. you're seeing a problem that simply isn't
there.
On Thu, 2004-07-15 at 07:49, Jim Ewert wrote:
> With pg_autovaccum it's now at 95M swap; averaging 5MB / day increase with same load. Cache slightly increases or decreases according to top.
>
> --- On Tue 07/13, Matthew T. O'Connor < matthew@zeut.net > wrote:
> From: Matthew T. O'Connor [mailto: matthew@zeut.net]
> To: jim.ewert@excite.com
> Cc: pgsql-performance@postgresql.org
> Date: Tue, 13 Jul 2004 16:26:09 -0400
> Subject: Re: [PERFORM] Swapping in 7.4.3
>
> Jim Ewert wrote:<br>> When I went to 7.4.3 (Slackware 9.1) w/ JDBC, the improvements are that it doesn't initially take much memory (have 512M) and didn't swap. I ran a full vaccum and a cluster before installation, however speed degaded to 1 *second* / update of one row in 150 rows of data, within a day! pg_autovacuum now gives excellent performance however it is taking 66M of swap; only 270k cached.<br>> <br><br>Are you saying that your system stays fast now that you are using <br>pg_autovacuum, but pg_autovacuum is using 66M of memory? Please <br>clarify, I'm not sure what question you want an answered.<br><br>Matthew<br><br>
>
> _______________________________________________
> Join Excite! - http://www.excite.com
> The most personalized portal on the Web!
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
>
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Swapping in 7.4.3
@ 2004-07-16 07:35 Matt Clark <matt@ymogen.net>
parent: Scott Marlowe <smarlowe@qwest.net>
0 siblings, 0 replies; 5+ messages in thread
From: Matt Clark @ 2004-07-16 07:35 UTC (permalink / raw)
To: 'Scott Marlowe' <smarlowe@qwest.net>; jim.ewert@excite.com; +Cc: matthew@zeut.net; pgsql-performance
> This is normal. My personal workstation has been up for 16
> days, and it shows 65 megs used for swap. The linux kernel
> looks for things that haven't been accessed in quite a while
> and tosses them into swap to free up the memory for other uses.
>
> This isn't PostgreSQL's fault, or anything elses. It's how a
> typical Unix kernel works. I.e. you're seeing a problem that
> simply isn't there.
Actually it (and other OSes) does slightly better than that. It _copies_
the least recently used pages into swap, but leaves them in memory. Then
when there really is a need to swap stuff out there is no need to actually
write to swap because it's already been done, and conversely if those pages
are wanted then they don't have to be read from disk because they were never
removed from memory.
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2004-07-16 07:35 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2004-07-12 16:59 Swapping in 7.4.3 Jim Ewert <jim.ewert@excite.com>
2004-07-13 20:26 ` Matthew T. O'Connor <matthew@zeut.net>
2004-07-15 13:49 Re: Swapping in 7.4.3 Jim Ewert <jim.ewert@excite.com>
2004-07-15 16:20 ` Scott Marlowe <smarlowe@qwest.net>
2004-07-16 07:35 ` Matt Clark <matt@ymogen.net>
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