2005 Network Servers 
Dynatrace
APRIL 2, 2020
For two decades, Dynatrace NAM—Network Application Monitoring, formerly known as DC RUM—has been successfully monitoring the user experience of our customers’ enterprise applications. SNMP managed the costs of network links well, but not the sources of those costs (i.e., Dynatrace news. Performance has always mattered.
All Things Distributed
AUGUST 17, 2011
No Server Required - Jekyll & Amazon S3. Amazon S3 is much more than just storage; the network and distributed systems infrastructure to ensure that content can be served fast and at high rates without customers impacting each other, is amazing. No Server Required. All Things Distributed. Comments (). Amazon S3 FTW!
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Brendan Gregg
NOVEMBER 29, 2017
It's amazing to recall that it was even possible to virtualize x86 before processors had hardware-assisted virtualization (Intel VT-x and AMD-V), which were added in 2005 and 2006. But not all workloads: some are network bound (proxies) and storage bound (databases). ## 5. AWS called this [enhanced networking]. The first was c3.
Rigor
JANUARY 13, 2020
These are the bestsellers in the web performance field, including the good old Speed Up Your Site (2003) by Andy King; Steve Souders’ Even Faster Web Sites (2009) ; Ilya Grigorik’s High Performance Browser Networking (2013) ; Tammy Everts’ Time is Money (2016) ; and a handful of more recent publications. Responsive and Fast.
ScaleOut Software
JUNE 22, 2020
The pace of these changes has made it challenging for server-based infrastructures to manage fast-growing populations of users and data sources while maintaining fast response times. They transparently distribute stored objects across the cluster’s servers and ensure that data is not lost if a server or network component fails.
ScaleOut Software
JUNE 22, 2020
The pace of these changes has made it challenging for server-based infrastructures to manage fast-growing populations of users and data sources while maintaining fast response times. They transparently distribute stored objects across the cluster’s servers and ensure that data is not lost if a server or network component fails.
Brendan Gregg
AUGUST 8, 2017
The oldest change in the entire Linux repo dates back to 2005, when Linus imported Linux 2.6.12-rc2, Thankfully, I found some older linux-devel mailing list archives, rescued from server backups, often stored as tarballs of digests. 90491 N|rnberg (Germany) Consulting+Networking+Programming+etc'ing 42. Network I/O?
Expert insights. Personalized for you.
167 
Let's personalize your content