Jeff Geerling puts the Compute Module 4 through its paces and compares it to the Raspberry Pi 4 and Compute Module 3+, highlighting some great new features like a PCI Express 1x slot on the IO board and NVMe support.

Content index:

  • 00:00 – Introduction
  • 03:29 – A Complete Redesign
  • 04:35 – PCIe, USB 3, and NVMe
  • 10:04 – Networking – Wired and Wireless
  • 12:37 – CPU Performance
  • 13:41 – eMMC Performance
  • 14:54 – USB Boot
  • 15:50 – NAS/NFS Performance
  • 17:05 – IO Board Features
  • 19:47 – Summary and Final Thoughts
  • 20:50 – Bloopers

How do you incorporate load testing into your DevOps pipeline?

In this episode, Tim Koopmans walks us through the steps of writing a browser-based load testing script using Flood Element, adding it as a task in Azure Pipelines, and ramping it up using Tricentis Flood. Running load tests continuously allows teams to easily spot performance degradation over time.

Jump To

  • [01:39] Overview of Flood platform
  • [02:55] What load testing can show you: Flood analytics
  • [04:44] Aspects of Performance (PEARS): what should you test for?
  • [05:38] Browser-level load testing with Flood Element
  • [06:29] DevOps Starter Pack + Azure Pipelines + Flood
  • [09:02] Writing a load testing script using Flood Element
  • [13:45] Adding load testing execution step to Azure DevOps pipeline using Flood API
  • [16:16] Scaling up load tests or keeping it small for continuous testing
  • [20:07] The value of including load testing in your DevOps pipelines

More Information:

GraphQL is a query language that is rapidly gaining wide adoption across the community.

It combines type validation with a query and filtering syntax that makes it easy to get up-and-running with a powerful web API in almost no time.

Features like running parallel queries or update-all become much easier because they are first-class citizens of GraphQL. Add to that a vibrant community that keeps creating excellent tooling and documentation, it’s clear why GraphQL has become so popular with developers

Every abstraction has a cost, and GraphQL is no exception. The added complexity and a new schema format to parse and execute mean new performance bottlenecks. In addition to performance issues, the wrong use of GraphQL can lead to architectural bottlenecks.

Instead of viewing this as a problem, NearForm took this as a challenge.

More details: