From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [Development] Fwd: samba tuning
Date: Thu, 22 Mar 2012 11:05:08 +0100 [thread overview]
Message-ID: <1332410708.16918.92.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <4F6AEC26.3080109@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1538 bytes --]
Hi,
I guess nobody ever checked them out.
For at least sendfile: I believe that the first kernels that came with
IPFire 2.1 did not have an implementation of sendfile.
I additionally found, that the buffers are set to approx. 8kb which
could also be increased. Supposedly, everyone has got enough of RAM.
Please open a bug to track this feature and prepare a patch.
Michael
On Thu, 2012-03-22 at 10:08 +0100, WhyTea wrote:
> Hi again!
>
> I've tested it again. Now with 1GBit/s
>
> without these parameters the write speed is about 23 MByte/s
> withe these parameters the write speed is about 80 MByte/s
>
> So I ask again, is there any reason why we don't use them?
>
> - Daniel
>
> -------- Original-Nachricht --------
> Betreff:
> samba tuning
> Datum:
> Wed, 14 Mar 2012 13:34:17 +0100
> Von:
> Daniel Weismüller
> <whytea(a)ipfire.org>
> Antwort an:
> whytea(a)ipfire.org
> An:
> development(a)lists.ipfire.org
>
>
> Hi all,
>
> is there any reason why ipfire don't use the following parameters with
> samba?
>
> use sendfile = 1
> aio read size = 1
> aio write size = 1
>
> I've tested them and it brings my samba-performance from 8,9 MB/s up to
> 9,2 MB/s (using 100Mbit/s fullduplex)
>
> - Daniel
>
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
next parent reply other threads:[~2012-03-22 10:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4F6AEC26.3080109@ipfire.org>
2012-03-22 10:05 ` Michael Tremer [this message]
2012-03-22 10:50 ` Christian Schmidt
2012-03-22 10:55 ` Michael Tremer
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=1332410708.16918.92.camel@rice-oxley.tremer.info \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/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