A colleague at work has been researching the nature of some issues we're
seeing in a FreeBSD/amd64 release/8.2.0 environment in which amd (which
is providing services to a jail, where the "useful work" actually gets
done) is apparently failing (on occasion) to perform the work it is
supposed to do
On Tue, 3 Jan 2012, Marc Olzheim wrote:
On Tue, Jan 03, 2012 at 12:21:10AM -0800, Garrett Cooper wrote:
The file is 3.0GB in size. Look at all those page faults though!
Thanks!
-Garrett
From usr.bin/cmp/c_regular.c:
#define MMAP_CHUNK (8*1024*1024)
...
for (..) {
mmap() chunk of
On 3 January 2012 00:34, Marc Olzheim wrote:
> On Tue, Jan 03, 2012 at 12:21:10AM -0800, Garrett Cooper wrote:
>> The file is 3.0GB in size. Look at all those page faults though!
>> Thanks!
>> -Garrett
>
> From usr.bin/cmp/c_regular.c:
>
> #define MMAP_CHUNK (8*1024*1024)
> ...
> for (..) {
>
On Tue, Jan 03, 2012 at 12:21:10AM -0800, Garrett Cooper wrote:
> The file is 3.0GB in size. Look at all those page faults though!
> Thanks!
> -Garrett
From usr.bin/cmp/c_regular.c:
#define MMAP_CHUNK (8*1024*1024)
...
for (..) {
mmap() chunk of size MMAP_CHUNK.
compare
On Mon, Jan 2, 2012 at 11:37 PM, Dieter BSD wrote:
> Task: cp(1) a several-GB file from one drive to another,
> then run cmp(1) to verify. Cp runs as expected, but
> cmp runs slower than expected. Neither the disks
> nor the cpu is maxed out. Local drives, no network
> involved
