Hi,
There seems to be some serious degradation in performance.
Under 7.0 I get about 90 MB/s (on write), while, on the same machine
under 7.1 it drops to 20!
Any ideas?
thanks,
danny
___
freebsd-stable@freebsd.org mailing list
There seems to be some serious degradation in performance.
Under 7.0 I get about 90 MB/s (on write), while, on the same machine
under 7.1 it drops to 20!
Any ideas?
Can you compare performanc with tcp?
--
regards
Claus
When lenity and cruelty play for a kingdom,
the gentler gamester
On Fri, Sep 26, 2008 at 10:04:16AM +0300, Danny Braniss wrote:
Hi,
There seems to be some serious degradation in performance.
Under 7.0 I get about 90 MB/s (on write), while, on the same machine
under 7.1 it drops to 20!
Any ideas?
1) Network card driver changes,
2) This could be
Jeremy Chadwick wrote:
On Thu, Sep 25, 2008 at 04:14:02PM +0200, Bartosz Stec wrote:
Your options are:
1) Consider increasing it from 512M to something like 1.5GB; do not
increase it past that on RELENG_7, as there isn't support for more than
2GB total. For example, on a 1GB memory
On Fri, Sep 26, 2008 at 10:04:16AM +0300, Danny Braniss wrote:
Hi,
There seems to be some serious degradation in performance.
Under 7.0 I get about 90 MB/s (on write), while, on the same machine
under 7.1 it drops to 20!
Any ideas?
1) Network card driver changes,
could be, but at
On 09/25/08 15:14, Andreas Rudisch wrote:
On Thu, 25 Sep 2008 12:49:42 +0200
Tobias Roth [EMAIL PROTECTED] wrote:
heh, that should be RELENG_7.
Update your source tree again and clean up the build dirs.
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html#Q23.4.14.6.
On Fri, Sep 26, 2008 at 12:27:08PM +0300, Danny Braniss wrote:
On Fri, Sep 26, 2008 at 10:04:16AM +0300, Danny Braniss wrote:
Hi,
There seems to be some serious degradation in performance.
Under 7.0 I get about 90 MB/s (on write), while, on the same machine
under 7.1 it drops to
On Fri, Sep 26, 2008 at 11:46:28AM +0200, Tobias Roth wrote:
On 09/25/08 15:14, Andreas Rudisch wrote:
On Thu, 25 Sep 2008 12:49:42 +0200
Tobias Roth [EMAIL PROTECTED] wrote:
heh, that should be RELENG_7.
Update your source tree again and clean up the build dirs.
On Thu, 25 Sep 2008, [EMAIL PROTECTED] wrote:
After cvsuping the source and recompiling the kernel from 7.0
pid 971 (kldstat), uid 0: exited on signal 11 (core dumped)
fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8
pid 977 (mdconfig), uid 0: exited on signal 11 (core dumped)
pid 978 (mdconfig),
On 09/26/08 11:59, Jeremy Chadwick wrote:
On Fri, Sep 26, 2008 at 11:46:28AM +0200, Tobias Roth wrote:
On 09/25/08 15:14, Andreas Rudisch wrote:
On Thu, 25 Sep 2008 12:49:42 +0200
Tobias Roth [EMAIL PROTECTED] wrote:
heh, that should be RELENG_7.
Update your source tree again and clean up
Hi all,
i'm trying to remotely upgrade a 5.5 system to 6.3 and have run into an
issue with userland not matching my kernel. (Yes i know i am a bad guy for
even trying to do a upgrade remote, but this is a dress rehersal for
future such scenarios.)
Symptoms:
When trying to ssh to the
Hello,
I have a VERY strange behaving 6-3p3 with DMA tmieouts and network cards
'dropping traffic'.
Following is the explanation of hardware and the thinga that are happening.
The machine is DELL optiplex PII 300mHZ with 512RAM.
It has 3 NICs:
fxp0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST
Hi all,
I'm traying to update a FreeBSD server box from 6.3p11 to 7.0 and I've
found a rare problems.
1) I do the sync process with csup(1); next I go into
/usr/src/sys/amd64/conf to edit the GENERIC file (I use a custimized
kernels) and this file doesn't exists. Mmmm I decide to repeat
On Fri, Sep 26, 2008 at 12:22:55PM +0200, Jordi Espasa Clofent wrote:
Hi all,
I'm traying to update a FreeBSD server box from 6.3p11 to 7.0 and I've
found a rare problems.
1) I do the sync process with csup(1); next I go into
/usr/src/sys/amd64/conf to edit the GENERIC file (I use a
On Fri, Sep 26, 2008 at 12:14:49PM +0200, Tobias Roth wrote:
On 09/26/08 11:59, Jeremy Chadwick wrote:
On Fri, Sep 26, 2008 at 11:46:28AM +0200, Tobias Roth wrote:
On 09/25/08 15:14, Andreas Rudisch wrote:
On Thu, 25 Sep 2008 12:49:42 +0200
Tobias Roth [EMAIL PROTECTED] wrote:
heh, that
On Fri, Sep 26, 2008 at 01:12:14PM +0300, Anton - Valqk wrote:
Hello,
I have a VERY strange behaving 6-3p3 with DMA tmieouts and network cards
'dropping traffic'.
The disk errors you see are well-known, but the reasons for them
happening differ per person. Some people replace cables and the
On 2008-Sep-26 12:22:55 +0200, Jordi Espasa Clofent [EMAIL PROTECTED] wrote:
1) I do the sync process with csup(1); next I go into
/usr/src/sys/amd64/conf to edit the GENERIC file (I use a custimized
kernels) and this file doesn't exists.
You might like to check your CVSup site against
I would do the following:
rm -fr /usr/src/*
rm -fr /var/db/sup/src-all
csup -h cvsupserver -L 2 -g /usr/share/examples/stable-supfile
I've done it. But the results are, at least, curious...
# csup -h cvsup.de.FreeBSD.org -L 2 -g
/usr/share/examples/cvsup/stable-supfile
Parsing supfile
On 2008-Sep-26 13:23:12 +0200, Jordi Espasa Clofent [EMAIL PROTECTED] wrote:
Connecting to cvsup.de.FreeBSD.org
Edwin's script reports this as up-to-date.
# cd /usr/src ; ls -la
total 0
But something is obviously wrong. Can you post your supfile please.
--
Peter Jeremy
Please excuse any
On Fri, Sep 26, 2008 at 01:23:12PM +0200, Jordi Espasa Clofent wrote:
I would do the following:
rm -fr /usr/src/*
rm -fr /var/db/sup/src-all
csup -h cvsupserver -L 2 -g /usr/share/examples/stable-supfile
I've done it. But the results are, at least, curious...
# csup -h
On Fri, 2008-09-26 at 10:04 +0300, Danny Braniss wrote:
Hi,
There seems to be some serious degradation in performance.
Under 7.0 I get about 90 MB/s (on write), while, on the same machine
under 7.1 it drops to 20!
Any ideas?
The scheduler has been changed to ULE, and NFS has
Finally I've modified the stable-supfile TAG from
*default release=cvs tag=RELENG_7_0
to
*default release=cvs tag=RELENG_7
and... voilà!... it works!
I've interrupted the csup process (^C) and change again the tag to
*default release=cvs tag=RELENG_7_0
and it works perfecty.
Maybe it's so
On Fri, Sep 26, 2008 at 02:12:08PM +0200, Jordi Espasa Clofent wrote:
Finally I've modified the stable-supfile TAG from
*default release=cvs tag=RELENG_7_0
to
*default release=cvs tag=RELENG_7
and... voilà!... it works!
I've interrupted the csup process (^C) and change again the tag to
Thanks Jeremy and Peter,
you are right that the machine has *lots* ot hardware in it,
I was thinking of the power supply as a reason and measured the 5 and 12
volts - seemd to be ok 11.8 and 5.2 with all hardware in it.
The shared irq is the one I've thought of and that's why I've posted
vmstat -i
On Fri, Sep 26, 2008 at 12:27:08PM +0300, Danny Braniss wrote:
On Fri, Sep 26, 2008 at 10:04:16AM +0300, Danny Braniss wrote:
Hi,
There seems to be some serious degradation in performance.
Under 7.0 I get about 90 MB/s (on write), while, on the same machine
under 7.1 it
On Fri, 2008-09-26 at 10:04 +0300, Danny Braniss wrote:
Hi,
There seems to be some serious degradation in performance.
Under 7.0 I get about 90 MB/s (on write), while, on the same machine
under 7.1 it drops to 20!
Any ideas?
The scheduler has been changed to ULE, and NFS has
On Friday 26 September 2008 03:04:16 am Danny Braniss wrote:
Hi,
There seems to be some serious degradation in performance.
Under 7.0 I get about 90 MB/s (on write), while, on the same machine
under 7.1 it drops to 20!
Any ideas?
thanks,
danny
Perhaps use nfsstat to see if
On Fri, Sep 26, 2008 at 04:35:17PM +0300, Danny Braniss wrote:
On Fri, Sep 26, 2008 at 12:27:08PM +0300, Danny Braniss wrote:
On Fri, Sep 26, 2008 at 10:04:16AM +0300, Danny Braniss wrote:
Hi,
There seems to be some serious degradation in performance.
Under 7.0 I get
On Fri, Sep 26, 2008 at 12:27:08PM +0300, Danny Braniss wrote:
On Fri, Sep 26, 2008 at 10:04:16AM +0300, Danny Braniss wrote:
Hi,
There seems to be some serious degradation in performance.
Under 7.0 I get about 90 MB/s (on write), while, on the same machine
under 7.1 it
Hi All
Jeremy Chadwick wrote:
On Thu, Sep 25, 2008 at 05:36:44PM +0200, Julian Stacey wrote:
Hi stable@,
I just imported an old tower from a friend. Used to run Linux OK.
Reset BIOS to defaults, turned off power saving etc, installed
7.1-BETA-i386-disc1.iso
I now sees
rl0:
On Sep 26, 2008, at 4:43 AM, Bartosz Stec wrote:
Jeremy Chadwick wrote:
These are the tuning settings I use:
vm.kmem_size=1536M
vm.kmem_size_max=1536M
vfs.zfs.arc_min=16M
vfs.zfs.arc_max=64M
Yesterday I've added 512 MB memory to box (sum 1,5GB), and set
vm.kmem_size and vm.kmem_size to
On 09/26/08 12:49, Jeremy Chadwick wrote:
Being as I just rebuilt world only 2 days ago and I did not run into
this problem, I'm concluding the issue must be with your system. :-)
It's possible you've done some bizarre tuning in /etc/make.conf or
/etc/src.conf which is somehow breaking the
Hello,
I decided to give 7.1-PRERELEASE a try on one of my machines to find
out if there might be any problems I should be aware of.
I quickly ran into problems. After a while the system freezes
completely. It seems to be somehow related to the load of the machine
as it doesn't seem to happen
I'm remaking binaries,
New generic kernel built installed, install of all src/ done too.
No improvement.
Is there reliable way to reproduce the issue?
Its continuous, the machine virtually never does a ping in less
than 10 seconds.
Anyway, would you try attached patch and let me know
Hi,
Reference:
From: Julian Stacey [EMAIL PROTECTED]
Date: Fri, 26 Sep 2008 19:16:57 +0200
Message-id: [EMAIL PROTECTED]
Julian Stacey wrote:
I'm remaking binaries,
New generic kernel built installed, install of all src/ done too.
No improvement.
Is there
- Original Message
From: Julian Stacey [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Friday, September 26, 2008 8:16:57 PM
Subject: Re: rl0: watchdog timeout + 40, 000 ms ping with
7.1-BETA-i386-disc1.iso
I'm remaking binaries,
New generic kernel
: -vfs.nfs.realign_test: 22141777
: +vfs.nfs.realign_test: 498351
:
: -vfs.nfsrv.realign_test: 5005908
: +vfs.nfsrv.realign_test: 0
:
: +vfs.nfsrv.commit_miss: 0
: +vfs.nfsrv.commit_blks: 0
:
: changing them did nothing - or at least with respect to nfs throughput
Just an effort to test RELENG_6 . No issues noted on my Dell server.
Nice work folks!
Copyright (c) 1992-2008 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a
On Fri, Sep 26, 2008 at 04:35:17PM +0300, Danny Braniss wrote:
I know, but I get about 1mgb, which seems somewhat low :-(
Since UDP has no way to know how fast to send, you need to tell iperf
how fast to send the packets. I think 1Mbps is the default speed.
David.
Hi Anton,
On 2008-Sep-26 15:13:19 +0300, Anton - Valqk [EMAIL PROTECTED] wrote:
you are right that the machine has *lots* ot hardware in it,
I was thinking of the power supply as a reason and measured the 5 and 12
volts - seemd to be ok 11.8 and 5.2 with all hardware in it.
A multimeter won't
David,
You beat me to it.
Danny, read the iperf man page:
-b, --bandwidth n[KM]
set target bandwidth to n bits/sec (default 1 Mbit/sec). This
setting requires UDP (-u).
The page needs updating, though. It should read -b, --bandwidth
n[KMG]. It also does NOT
On 2008-Sep-26 13:12:14 +0300, Anton - Valqk [EMAIL PROTECTED] wrote:
1. I get a lot of dma times outs. mostly on ad5 and ad7 where I keep
...
dmesg.today:ad7: FAILURE - WRITE_DMA48 status=51READY,DSC,ERROR
error=10NID_NOT_FOUND LBA=374303456
This is a bad sign and suggests dying disk but...
2.
By default FreeBSD 7.0 shipped with the sysctls set to:
kern.maxfiles: 12328
kern.maxfilesperproc: 11095
We recently bumped up against these limits in an unfortunate way and
we are going to raise them. I have some questions:
* why are the numbers set the way they are? They aren't round
On Fri, Sep 26, 2008 at 06:21:01PM +0200, Christian Laursen wrote:
I decided to give 7.1-PRERELEASE a try on one of my machines to find
out if there might be any problems I should be aware of.
I quickly ran into problems. After a while the system freezes
completely. It seems to be somehow
On Sat, Sep 27, 2008 at 11:10:01AM +1000, Aristedes Maniatis wrote:
By default FreeBSD 7.0 shipped with the sysctls set to:
kern.maxfiles: 12328
kern.maxfilesperproc: 11095
We recently bumped up against these limits in an unfortunate way and we
are going to raise them. I have some
Hello Jeremy,
Sunday, September 21, 2008, 3:07:20 PM, you wrote:
Consider using background_fsck=no in /etc/rc.conf if you prefer the
old behaviour. Otherwise, boot single-user then do the fsck.
Actually what's the advantage of having fsck run in background if it
isn't capable of fixing
On Fri, Sep 26, 2008 at 09:33:41PM -0700, Derek Kuli??ski wrote:
Hello Jeremy,
Sunday, September 21, 2008, 3:07:20 PM, you wrote:
Consider using background_fsck=no in /etc/rc.conf if you prefer the
old behaviour. Otherwise, boot single-user then do the fsck.
Actually what's the
Hello Jeremy,
Friday, September 26, 2008, 10:14:13 PM, you wrote:
Actually what's the advantage of having fsck run in background if it
isn't capable of fixing things?
Isn't it more dangerous to be it like that? i.e. administrator might
not notice the problem; also filesystem could break even
48 matches
Mail list logo
