The trouble is that there's lots of anecdotal evidence, but noone's
really gone digging deep into _their_ example of why it's broken. The
developers who know this stuff don't see anything wrong. That hints to
me it may be something a little more creepy - as an example, the
interplay between netisr/
On Sun Dec 18 11, Alexander Best wrote:
> On Sun Dec 18 11, Andrey Chernov wrote:
> > On Sun, Dec 18, 2011 at 05:51:47PM +1100, Ian Smith wrote:
> > > On Sun, 18 Dec 2011 02:37:52 +, Bruce Cran wrote:
> > > > On 13/12/2011 09:00, Andrey Chernov wrote:
> > > > > I observe ULE interactivity slo
Thanks.
My request for the person documenting the tunings also runs = the
benchmark to ensure expected behaviour.
The installation, execut= ion and comparison against the benchmarks in
the article is fairly simple.<= br>
Note that some tuning may not be relevant or recommended (i
On Thu, Dec 15, 2011 at 10:46 AM, Chris Rees wrote:
> On 15 December 2011 17:58, O. Hartmann wrote:
>> Since ZFS in Linux can only be achieved via FUSE (ad far as I know), it
>> is legitimate to compare ZFS and ext4. It would be much more competetive
>> to compare Linux BTRFS and FreeBSD ZFS.
>>
15.12.2011 15:48, Jeremy Chadwick wrote:
I'm getting to the point where I'm considering formulating a private
mail to Jeff Roberson, requesting that he be aware of the discussion
that's happening (not that he necessarily follow or read it), and that
based on what I can tell we're at a roadblock -
On Dec 15, 2011, at 3:48 PM, Jeremy Chadwick wrote:
[…]
> That said: thrown out, data ignored, done.
>
> Now what? Where are we? We're right back where we were a day or two
> ago; meaning no closer to solving the dilemma reported by users and
> SCHED_ULE. Heck, we're not even sure if there is
On 12/15/2011 08:26 AM, Sergey Matveychuk wrote:
15.12.2011 17:36, Michael Larabel пишет:
On 12/15/2011 07:25 AM, Stefan Esser wrote:
Am 15.12.2011 11:10, schrieb Michael Larabel:
No, the same hardware was used for each OS.
In terms of the software, the stock software stack for each OS was
u
On Thu, Dec 15, 2011 at 05:32:47AM -0700, Samuel J. Greear wrote:
> > Well, the only way it's going to get fixed is if someone sits down,
> > replicates it, and starts to document exactly what it is that these
> > benchmarks are/aren't doing.
> >
>
> I think you will find that investigation is lar
Am 15.12.2011 11:10, schrieb Michael Larabel:
> No, the same hardware was used for each OS.
>
> In terms of the software, the stock software stack for each OS was used.
Just curious: Why did you choose ZFS on FreeBSD, while UFS2 (with
journaling enabled) should be an obvious choice since it is mo
On 12/15/2011 07:25 AM, Stefan Esser wrote:
Am 15.12.2011 11:10, schrieb Michael Larabel:
No, the same hardware was used for each OS.
In terms of the software, the stock software stack for each OS was used.
Just curious: Why did you choose ZFS on FreeBSD, while UFS2 (with
journaling enabled) s
Hi, all,
Am 15.12.2011 um 12:18 schrieb Michael Ross:
> Following Steven Hartlands' suggestion,
> from one of my machines:
>
> /usr/ports/sysutils/dmidecode/#sysctl -a | egrep "hw.vendor|hw.product"
>
> /usr/ports/sysutils/dmidecode/#dmidecode -t 2
> # dmidecode 2.11
> SMBIOS 2.6 present.
>
> H
On 12/15/2011 04:41 AM, Michael Ross wrote:
Am 15.12.2011, 11:10 Uhr, schrieb Michael Larabel
:
On 12/15/2011 02:48 AM, Michael Ross wrote:
Anyway these tests were performed on different hardware, FWIW.
And with different filesystems, different compilers, different GUIs...
No, the same
On Sun Dec 18 11, Andrey Chernov wrote:
> On Sun, Dec 18, 2011 at 05:51:47PM +1100, Ian Smith wrote:
> > On Sun, 18 Dec 2011 02:37:52 +, Bruce Cran wrote:
> > > On 13/12/2011 09:00, Andrey Chernov wrote:
> > > > I observe ULE interactivity slowness even on single core machine
> > (Pentium
>
Am 16.12.2011 08:06, schrieb O. Hartmann:
> For the underlying OS, as far as I know, the compiler hasn't as much
> impact as on userland software since autovectorization and other neat
> things are not used during system build.
>
> From my experience using gcc 4.2 or 4.4/4.5 does not have an impac
On Thu, Dec 15, 2011 at 9:58 PM, Mike Tancsa wrote:
> On 12/15/2011 11:56 AM, Attilio Rao wrote:
>> So, as very first thing, can you try the following:
>> - Same codebase, etc. etc.
>> - Make the test 4 times, discard the first and ministat for the other 3
>> - Reboot
>> - Change the steal_thresh
On Thu, Dec 15, 2011 at 05:26:27PM +0100, Attilio Rao wrote:
> 2011/12/13 Jeremy Chadwick :
> > On Mon, Dec 12, 2011 at 02:47:57PM +0100, O. Hartmann wrote:
> >> > Not fully right, boinc defaults to run on idprio 31 so this isn't an
> >> > issue. And yes, there are cases where SCHED_ULE shows much
On Dec 15, 2011, at 3:25 PM, Stefan Esser wrote:
> Am 15.12.2011 11:10, schrieb Michael Larabel:
>> No, the same hardware was used for each OS.
>>
>> In terms of the software, the stock software stack for each OS was used.
>
> Just curious: Why did you choose ZFS on FreeBSD, while UFS2 (with
>
> Well, the only way it's going to get fixed is if someone sits down,
> replicates it, and starts to document exactly what it is that these
> benchmarks are/aren't doing.
>
I think you will find that investigation is largely a waste of time,
because not only are some of these benchmarks just downr
On Thu, Dec 15, 2011 at 04:55:16AM -0600, Michael Larabel wrote:
> On 12/15/2011 04:41 AM, Michael Ross wrote:
> >Am 15.12.2011, 11:10 Uhr, schrieb Michael Larabel
> >:
> >
> >>On 12/15/2011 02:48 AM, Michael Ross wrote:
> >
> >>>Anyway these tests were performed on different hardware, FWIW.
> >>>A
Am 15.12.2011, 11:55 Uhr, schrieb Michael Larabel
:
On 12/15/2011 04:41 AM, Michael Ross wrote:
Am 15.12.2011, 11:10 Uhr, schrieb Michael Larabel
:
On 12/15/2011 02:48 AM, Michael Ross wrote:
Anyway these tests were performed on different hardware, FWIW.
And with different filesystems,
Am 15.12.2011, 11:10 Uhr, schrieb Michael Larabel
:
On 12/15/2011 02:48 AM, Michael Ross wrote:
Anyway these tests were performed on different hardware, FWIW.
And with different filesystems, different compilers, different GUIs...
No, the same hardware was used for each OS.
The pictur
Hi,
What Attilllo and others need are KTR traces in the most stripped down
example of interactive-busting workload you can find.
Eg: if you're doing 32 concurrent buildworlds and trying to test
interactivity - fine, but that's going to result in a lot of KTR
stuff.
If you can reproduce it using a
On 12/18/11 03:37, Bruce Cran wrote:
> On 13/12/2011 09:00, Andrey Chernov wrote:
>> I observe ULE interactivity slowness even on single core machine
>> (Pentium 4) in very visible places, like 'ps ax' output stucks in the
>> middle by ~1 second. When I switch back to SHED_4BSD, all slowness is
>>
On 18/12/2011 10:34, Adrian Chadd wrote:
I applaud reppie for trying to make it as easy as possible for people
to use KTR to provide scheduler traces for him to go digging with, so
please, if you have these issues and you can absolutely reproduce
them, please follow his instructions and work with
24 matches
Mail list logo
