Figure Out What Problem You’re Trying to Solve
A long while ago I got into an hilarious Tweetfest (note to self: don’t… not that I would ever listen) starting with:
Which feature and which Cisco router for layer2 extension over internet 100Mbps with 1500 Bytes MTU
The knee-jerk reaction was obvious: OMG, not again. The ugly ghost of BRouters (or is it RBridges or WAN Extenders?) has awoken. The best reply in this category was definitely:
I cannot fathom the conversation where this was a legitimate design option. May the odds forever be in your favor.
A dozen “this is a dumpster fire” tweets later the problem was rephrased as:
Read more ...End of term
My children broke up from school this past weekend, which seems as good a reason as any to call this ‘end of term’ for The Morning Paper. I’ll be taking a break until the New Year, topping up my reading lists and getting ready for a whole new crop of papers and discoveries. The Morning Paper will resume on Monday 6th January.
Since term began on the 19th August we’ve looked at 50 different papers, and I had the pleasure of attending VLDB and HPTS in person as well. I learned a ton! I hope you found something you enjoyed in the paper selections as well.
Here’s a small selection of my personal highlights from the term, in case you missed any of them (in the order in which they originally appeared on the blog):
- Procella: unifying and serving analytical data at YouTube
- The secret-sharer: evaluating and testing unintended memorization in neural networks
- 150 successful machine learning models: lessons learned at Booking.com
- Stop explaining black box machine learning models for high stakes decisions and use interpretable models instead
- Local-first software: you own your data, in spite of the cloud
- Mergeable replicated data types
- Declarative assembly of web applications from Continue reading
Physically man-in-the-middling an IoT device with Linux Bridge
 |
| Initial setup |
network:
version: 2
renderer: networkd
ethernets:
eth0:
dhcp4: no
eth1:
dhcp4: no
bridges:
br0:
addresses: [192.168.1.2/24]
gateway4: 192.168.1.1
interfaces:
- eth0
- eth1
This is finally the year of the ARM server
"RISC" was an important architecture from the 1980s when CPUs had fewer than 100,000 transistors. By simplifying the instruction set, they free up transistors for more registers and better pipelining. It meant executing more instructions, but more than making up for this by executing them faster.But once CPUs exceed a million transistors around 1995, they moved to Out-of-Order, superscalar architectures. OoO replaces RISC by decoupling the front-end instruction-set with the back-end execution. A "reduced instruction set" no longer matters, the backend architecture differs little between Intel and competing RISC chips like ARM. Yet people have remained fixated on instruction set. The reason is simply politics. Intel has been the dominant instruction set for the computers we use on servers, desktops, and laptops. Many instinctively resist whoever dominates. In addition, colleges indoctrinate students on the superiority of RISC. Much college computer science instruction is decades out of date.
For 10 years, the ignorant press has been championing the cause of ARM's RISC processors in servers. The refrain has always been that RISC has some inherent power efficiency advantage, and that ARM processors with natural power efficiency from the mobile world will be more power efficient for the data center.
None Continue reading
Samsung Expands 5G Footprint With Videotron
Samsung will provide massive MIMO and dual-band base stations to support the operator’s 4G LTE...
Amping Up The Arm Server Roadmap
Competition in and of itself does not directly drive innovation – customer needs that might be met by some other product is really what makes suppliers hop to and get the lead out. …
Amping Up The Arm Server Roadmap was written by Timothy Prickett Morgan at The Next Platform.
Google Transfer Service Mitigates Cloud Migration Migraines
Transfer Service aims to removes inherent complexities with large-scale data transfers and moving...
Heavy Networking 494: Hybrid Cloud Networking – All The Details
Today's Heavy Networking drills into routing complexities and options for hybrid cloud networking. Our guest is William Collins, lead cloud architect at a large healthcare company. He shares his experiences connecting resources on premises to public cloud services. We also discuss the importance of design and governance, and why your networking skills are absolutely critical when it comes to the cloud.
The post Heavy Networking 494: Hybrid Cloud Networking – All The Details appeared first on Packet Pushers.
Amazon Leads Linux Foundation’s Edge NOS Project
DENT will use the Linux Kernel and other Linux-based projects as the basis for the open source NOS,...
Service to service communication within GKE cluster
In my last blog, I covered options to access GKE services from external world. In this blog, I will cover service to service communication options within GKE cluster. Specifically, I will cover the following options: Cluster IP Internal load balancer(ILB) Http internal load balancer Istio Traffic director In the end, I will also compare these … Continue reading Service to service communication within GKE clusterCiena Chief Calls Infinera 600G Uncompetitive Amid Strong Q4
Amid double-digital growth in 2019, Ciena CEO Gary Smith says Infinera's 600G optics lack the...
Weekly Wrap: Aviatrix CEO: SD-WAN Is Dead. AWS Killed It
SDxCentral Weekly Wrap for Dec. 13, 2019: AWS' Outposts, Wavelengths are the nail in SD-WAN's...
HPC In The Cloud Rolls Through An Inflection Point
Hyperion Research has declared 2019 as the year that high performance computing in the cloud hit a “tipping point.” Cloud spending for HPC work is projected to jump from just under $2.5 billion in 2018 to approximately $4 billion by the end of 2019. …
HPC In The Cloud Rolls Through An Inflection Point was written by Michael Feldman at The Next Platform.