From: "krautus@kr916.org" <krautus@kr916.org>
To: xfs@oss.sgi.com
Subject: all your slabs are belong to ram ?
Date: Tue, 6 Oct 2015 16:24:43 +0200 [thread overview]
Message-ID: <20151006162443.42f48ee7@linux> (raw)
Dear List, nice to meet you :)
First post, straight to the point:
I'm wrestling from few weeks with a problem: roundcube (a webmail client) takes too long to open a dovecot (pop/imap server) mailbox with many emails (files).
So, when such user has more than 10K emails, it takes around 1 minute to open the mailbox.
Meanwhile, I/O %util goes to 100% and bottlenecks the whole system.
I've tried memcache(d) integration with roundcube but it doesn't eliminate the problem.
OS is Debian Wheezy 32-bit, 16GB of ECC RAM and storage is a simple hardware raid-1 with a couple of sata2 hard disks.
I've just used mkfs.xfs (with no tuning) and no options while mounting (in fstab).
It looks like the problem is the slow access to dentries and inodes, so I've set vfs_cache_pressure to 1,
forced buffering with few "find /var/mail > /dev/null"
and have it running like this from around 4 days.
Didn't help: slabs still gets flushed and opening folders is slow as before.
Current slabtop usage shows:
235352K used by xfs_inode
and
49708K used by dentry
while I would expect to have at least 1 GB of xfs_inode and at least 200MB of dentry.
So I'm asking you:
1. is there a way to force dentries and inodes to stay in ram ?
2. can I perhaps move dentries and inodes to a dedicated SSD ?
I'm open to all possibilities, perhaps increase RAM ?
Upgrade to Debian Jessie and 64 bit ?
Let me know if I can provide more info.
Thank you very much!
Mike
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2015-10-06 14:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 14:24 krautus [this message]
2015-10-06 14:50 ` all your slabs are belong to ram ? Darrick J. Wong
2015-10-06 16:16 ` Johannes Truschnigg
2015-10-06 18:34 ` krautus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151006162443.42f48ee7@linux \
--to=krautus@kr916.org \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox