I included networking-discuss@
On 28/12/2009 15:50, Saso Kiselkov wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Thank you for the advice. After trying flowadm the situation improved
somewhat, but I'm still getting occasional packet overflow (10-100
packets about every 10-15 minutes). This is somewhat unnerving, because
I don't know how to track it down.
Here are the flowadm settings I use:
# flowadm show-flow iptv
FLOW LINK IPADDR PROTO LPORT RPORT
DSFLD
iptv e1000g1 LCL:224.0.0.0/4 -- -- -- --
# flowadm show-flowprop iptv
FLOW PROPERTY VALUE DEFAULT POSSIBLE
iptv maxbw -- -- ?
iptv priority high -- high
I also tuned udp_max_buf to 256MB. All recording processes are boosted
to the RT priority class and zfs_txg_timeout=1 to force the system to
commit data to disk in smaller and more manageable chunks. Is there any
further tuning you could recommend?
Regards,
- --
Saso
I need all IP multicast input traffic on e1000g1 to get the highest
possible priority.
Markus Kovero wrote:
Hi, Try to add flow for traffic you want to get prioritized, I noticed that
opensolaris tends to drop network connectivity without priority flows defined,
I believe this is a feature presented by crossbow itself. flowadm is your
friend that is.
I found this particularly annoying if you monitor servers with icmp-ping and
high load causes checks to fail therefore triggering unnecessary alarms.
Yours
Markus Kovero
-----Original Message-----
From: zfs-discuss-boun...@opensolaris.org
[mailto:zfs-discuss-boun...@opensolaris.org] On Behalf Of Saso Kiselkov
Sent: 28. joulukuuta 2009 15:25
To: zfs-discuss@opensolaris.org
Subject: Re: [zfs-discuss] ZFS write bursts cause short app stalls
I progressed with testing a bit further and found that I was hitting
another scheduling bottleneck - the network. While the write burst was
running and ZFS was commiting data to disk, the server was dropping
incomming UDP packets ("netstat -s | grep udpInOverflows" grew by about
1000-2000 packets during every write burst).
To work around that I had to boost the scheduling priority of recorder
processes to the real-time class and I also had to lower
zfs_txg_timeout=1 (there was still minor packet drop after just doing
priocntl on the processes) to even out the CPU load.
Any ideas on why ZFS should completely thrash the network layer and make
it drop incomming packets?
Regards,
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAks406oACgkQRO8UcfzpOHBVFwCguUVlMhTt9PlcbcqUjJzJ8Oij
CiIAoJJFHu1wtLMbyOyhXbyDPTkSFSFc
=VLoO
-----END PGP SIGNATURE-----
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
