Oh, the perils of dd microbenchmarks! You've already demonstrated the /dev/zero
compression trap, but there's more...
It's not just compression you have to consider - e.g. something in your stack
may be converting regions of zeros to holes (though this doesn't appear to be
an issue for you
Thanks for these measurements and observations. I will suggest you forward
this mail to the Illumos developer list, for a wider audience.
Thanks!
Dan
Sent from my iPhone (typos, autocorrect, and all)
> On Apr 7, 2016, at 11:35 PM, Josh Coombs wrote:
>
> Hi all,
>
> I
Hi all,
I just recently kitbashed a backup storage dump based on OmniOS, a couple
retired servers and a few new bits to improve it's perf.
- HP DL360 G6 with dual Xeon 5540s, 80GB RAM
- The onboard HP SAS is hosting the root pool on it's RAID 5 of SAS disks,
not ideal but the card doesn't have
7 апреля 2016 г. 20:50:13 CEST, "Schweiss, Chip" пишет:
>On Thu, Apr 7, 2016 at 12:51 PM, Michael Talbott
>wrote:
>
>> Oh, I see. Sorry about that, reading it on my phone didn't render
>your
>> diagram properly ;)
>>
>> The reason this is happening is
I see. I know in the linux world, one could use iptables to tag packets coming
in on an interface and then route the response back out of the interface they
came in which would solve the issue (which I've done before to work around a
similar oddball issue), but, I have no idea if that sort of
Hi, sorry, I forget to modify the "to", to the list..
- Forwarded message from PÁSZTOR György
-
Date: Thu, 7 Apr 2016 21:36:55 +0200
From: PÁSZTOR György
To: "Schweiss, Chip"
Hi,
"Schweiss, Chip"
On Thu, Apr 7, 2016 at 12:51 PM, Michael Talbott wrote:
> Oh, I see. Sorry about that, reading it on my phone didn't render your
> diagram properly ;)
>
> The reason this is happening is because the omnios box has knowledge of
> both subnets in its routing table and it always
Oh, I see. Sorry about that, reading it on my phone didn't render your diagram
properly ;)
The reason this is happening is because the omnios box has knowledge of both
subnets in its routing table and it always takes the shortest path to reach an
ip destination.
So you will need to put the
It sounds like you're using the same subnet for management and service traffic,
that would be the problem causing the split route. Give each vlan a unique
subnet and traffic should flow correctly.
Michael
Sent from my iPhone
> On Apr 7, 2016, at 8:52 AM, Schweiss, Chip
Hello,
I learned recently that US government agencies cannot purchase equipment
that connects to their network unless said equipment is proven to work with
IPv6.
Suppliers must submit a Supplier's Declaration of Conformity (SDOC) which
shows that an accredited testing lab has qualified various
10 matches
Mail list logo