pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
fragmention issue with ext4: e4defrag?
2+ messages / 2 participants
[nested] [flat]

* fragmention issue with ext4: e4defrag?
@ 2014-07-02 08:51  Marc Mamin <M.Mamin@intershop.de>
  0 siblings, 1 reply; 2+ messages in thread

From: Marc Mamin @ 2014-07-02 08:51 UTC (permalink / raw)
  To: pgsql-performance

Hello,

Has anyone some experience using defragmentation tools on Linux against tablespaces ?

we are facing fragmentation problems with postgres instances having a few TB of data.
( RAID 5 )

I/O througput decreased from 300MB/s to 160.


- We first moved some schemas to separate servers.
  After that we still have  150'000 tables in 1.5 TB
  
- Now we are in the process of vacuuming FULL historical tables which are not written anymore. 
  This seems to improve the I/O considerably
  
Our remaining issue is that the free space fragmentíon is still suboptimal 
so that fragmention will probably start again soon.

Would it make sense to use a tool like e4defrag	
(http://www.linux.org/threads/online-defragmentation.4121/)
in order to defrag the free space ?
And how safe is it to use such a tool against a running postgres instance?



many thanks,

Marc Mamin


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance



^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: fragmention issue with ext4: e4defrag?
@ 2014-07-02 18:01  Kevin Grittner <kgrittn@ymail.com>
  parent: Marc Mamin <M.Mamin@intershop.de>
  0 siblings, 0 replies; 2+ messages in thread

From: Kevin Grittner @ 2014-07-02 18:01 UTC (permalink / raw)
  To: Marc Mamin <M.Mamin@intershop.de>; pgsql-performance

Marc Mamin <M.Mamin@intershop.de> wrote:

> I/O througput decreased from 300MB/s to 160.

I don't have any experience with ext4 defrag tools, but just wanted
to point out that the difference in performance you cite above is
about the same as the difference between accessing data on the
outer (and usually first-filled) tracks on a disk drive and the
inner tracks.  One of the reasons performance falls as a drive
fills is that the OS is compelled to use slower and slower portions
of the disk.  Part of the benefit you are seeing might be due to
freeing "fast" tracks and data being relocated there.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance



^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~2014-07-02 18:01 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2014-07-02 08:51 fragmention issue with ext4: e4defrag? Marc Mamin <M.Mamin@intershop.de>
2014-07-02 18:01 ` Kevin Grittner <kgrittn@ymail.com>

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