Our Virtual Edge Report is Live!
Download your free copy of the Virtual Edge Report today!
Download your free copy of the Virtual Edge Report today!
The former Cisco CTO drops a few hints at the Intel Capital Global Summit.
I've been bitten by this one. It happens when you quite naturally use the file system as a quick and dirty database. A directory is a lot like a table and a file name looks a lot like a key. You can store many-to-one relationships via subdirectories. And the path to a file makes a handy quick lookup key.
The problem is a file system isn't a database. That realization doesn't hit until you reach a threshold where there are actually lots of files. Everything works perfectly until then.
When the threshold is hit iterating a directory becomes very slow because most file system directory data structures are not optimized for the lots of small files case. And even opening a file becomes slow.
According to Steve Gibson on Security Now (@16:10) LastPass ran into this problem. LastPass stored every item in their vault in an individual file. This allowed standard file syncing technology to be used to update only the changed files. Updating a password changes just one file so only that file is synced.
Steve thinks this is a design mistake, but this approach makes perfect sense. It's simple and robust, which is good design given, what I assume, Continue reading
Read the full Q&A for Cisco's DemoFriday on achieving full WAN/MAN orchestration through utilizing SDN with Segment Routing.
Last year I claimed that you don’t need more than two switches in your data center (I’ll run a presentation on the same topic in a few days), but focused exclusively on the networking side of the equation.
Iwan Rahabok recently published a great blog post describing the compute- and storage parts of it. His conclusion: 1000 VM per rack is perfectly realistic.
In an earlier blog post, I discussed the issues associated with IPv6 packet fragmentation. Of particular significance, IPv6 fragmentation relies extensively on the computer sourcing packets being able to receive ICMPv6 “packet too big” message type 2 sent from any intermediate device in the route to the packet’s destination.
The capability to confirm that an end user in a network will correctly receive the packet-too-big ICMPv6 message has been added to the test-ipv6 mirrors, including http://test-ipv6.arbor.net. This new capability allows a user to identify if the packet-too-big message is being discarded between the user’s computer and the web site.
In the “Tests Run” tab of the main test-ipv6 mirror page, the “Test IPv6 large packet” test documents the IPv6 fragmentation behavior. If further information is desired, one can click on the “Technical Info” link.
If the “Test IPv6 large packet” test is failing, the packet-too-big ICMPv6 message is likely being dropped. This indicates issues within the user’s computer, enterprise network or elsewhere along the path to the test-ipv6 mirror. The problematic device may be a router or firewall device, although it may even be the “firewall” software configured on the user’s computer.
Any device in the Continue reading
Would you like to be a member of Computer Networking Forum which has many senior level network designer hanging out. It would be nice , right ? I have received [CONTINUE READING]
The post Computer Networking Forum and Live Chat appeared first on Network Design and Architecture.
I'll be live blogging from ONUG for this fall 2015 session. I'm in Manhattan already, looking forward to the event that starts on Wednesday. Refresh this page periodically to see the latest updates as I glean technical data from the presentations in real-time.
The post ONUG Fall 2015 Live Blog – Ethan Banks appeared first on Packet Pushers.
The post Worth Reading: IETF Yokohama Day 3 appeared first on 'net work.