![](https://seccdn.libravatar.org/avatar/7891b1b1a5767f4b9ac1cc0723cebdac.jpg?s=120&d=mm&r=g)
Greg Freemyer wrote:
On Thu, Mar 19, 2015 at 5:53 AM, Per Jessen
wrote: Felix Miata wrote:
Greg Freemyer composed on 2015-03-16 09:32 (UTC-0400):
If the workload is small 1 page writes, then the penalty is huge. For every write a read/modify/write cycle has to be implemented.
Is it really? What kind of use case produces many writes of different small files in sequence or short order?
Almost any database server.
I have a couple of mariadb/mysql installation, I don't think they do "many writes of different small files in sequence or short order". I mean, some, but the tables don't tend to be small files and the access is more random than sequential.
Untarring the kernel source tarball?
Yup.
Perhaps a busy email server.
I can tell you parsing 50GB of PST files on rotating rust can take days whereas the same workload goes to hours with SSD. (a few million seeks really adds up and most rotating drives can only do hundreds of random i/o's per second.)
I was thinking more of e.g. a postfix installation and the queue files. Or a dovecot ditto. -- Per Jessen, Zürich (15.1°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org