On Fri, Dec 23, 2011 at 10:00:05AM -0500, John Baldwin wrote:
> On Thursday, December 22, 2011 6:58:46 pm Jeremy Chadwick wrote:
> > On Fri, Dec 23, 2011 at 12:44:14AM +0100, O. Hartmann wrote:
> > > On 12/21/11 19:41, Alexander Leidinger wrote:
> > > > Hi,
> &g
clear:
>
> man make.conf(5) says, that MALLOC_PRODUCTION is a knob set in
> /etc/make.conf.
> The WiJi says, MALLOC_PRODUCTION is to be set in /etc/src.conf.
>
> What's right and what's wrong now?
I can say with certainty that this value belongs in /etc/make.conf
(on RE
ystem to
store logs/data results.
The KTR stuff Atillio and many others have requested, I think, will be
the most beneficial way to get the developers the data they need. I had
no idea about it until I found out that KTR was something completely
different than ktrace.
I still haven't found
ies
and provide the data somewhere central for devs to review. I only
mention this because so far I haven't seen anyone really say "okay, this
is what we should be using for these kinds of tests". Yay nature of the
beast.
--
| Jeremy Chadwickjdc at p
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, ther
rbour a
community of folks who are more argumentative/aggressive than, say,
Linux (generally speaking). In this thread though, I think all of us
really want to assist in some way to figure out what exactly is going on
here, scheduler-wise, and see if we can put something together to han
n 7.1-RELEASE
came out on 2009/01/05.
"All of the answers", in a roundabout and non-user-friendly way, are
available by examining the commit history for src/sys/kern/sched_ule.c.
It's hard to follow especially given that you have to consider all
the releases/branchpoints th
in as they see fit.
I know folks were focused mainly on buildworld.
I personally would find it interesting if someone with a higher-end
system (e.g. 2 physical CPUs, with 6 or 8 cores per CPU) was to do the
same test (changing -jX to -j{numofcores} of course).
--
| Jeremy Chadwick
chnical
innards/workings of GEOM since the documentation is so poor (and reading
the code doesn't help, especially with regards to libgeom).
IMHO, the gsched "stuff", as a "layer", should probably be moved into
the I/O framework by default, with t
, 112M Buf, 57M Free
Swap: 8192M Total, 228K Used, 8192M Free
Regarding why you're adding up all the individual process statistics: I
can imagine they would vary a slight bit, but I cannot explain a 7%
variance. Someone with more knowledge will have to assist there.
--
| Jeremy Chadwick
10 matches
Mail list logo
