> I just answered most of your questions on your help ticket, but it may be a 
> while before our support team passes my reply on
Not a problem- I wanted to get as much insight as possible and have somewhere 
to document my findings for anyone else that comes along.

> I believe those last 3 (pcplusmp*) are no longer required in this version of
> opensolaris, but they should check the web to confirm. See
> http://www.solarisinternals.com/wiki/index.php/Networks
I've been using the SolarisInternals wiki but some of the information seems out 
of date and/or contradictory to what Myricom recommends. For example:

Myricom recommends a tcp_recv_hiwat that is twice what the SolarisInternals 
wiki recommends. I'm using the Myricom recommendation.

SolarisInternals also recommends setting ip_soft_rings_cnt but I don't see it 
in ndd and it's commitment level is listed as obsolete here: 
http://download.oracle.com/docs/cd/E19082-01/819-2724/gbsbo/index.html

Does anyone know if this tunable still exists? I've tried querying ndd -get 
/dev/ip ? as well as a few other places and don't see it anywhere.

> I think b147 has fixed the 2 mblk chain limit that forces packets
> through a slow path in TCP, so you can probably increase that to 8.
I'll give that a try. Thanks.

> Some of these proposed settings (myri10ge_use_msix=0;
> myri10ge_max_slices=1;) disable multiple slices, and negate the
> ddi_msix_alloc_limit tuning. So do one or the other, but not both :)
Yes- I won't be using both- I was just trying to figure out which one made the 
most sense for my workload.

> Most of the "low latency" tuning suggestions you found are for workloads
> like HFT, where every microsecond matters. For a fileserver, I'd
> suggest optimizing for CPU utilization (eg, bandwidth).
And that is the exact bit of information I was looking for- Thanks!


-Don
-- 
This message posted from opensolaris.org
_______________________________________________
networking-discuss mailing list
[email protected]

Reply via email to