Profilers measure the performance of a program at runtime by adding instrumentation to collect information about the frequency and duration of function calls. They are crucial tools for understanding the real-world performance characteristics of code and are often the first step in optimizing a program. Apple and Google have first party profiling tools, but they are only usable for local debugging during development.
The 3-2-1 backup rule is a strategy to ensure your data is recoverable in case of data loss incidents. It recommends having at least: The rule was conceptualized by US photographer Peter Krogh. After initially impacting the photography world, Krogh’s idea was quickly adopted by other technology disciplines. It’s a great way to evaluate and manage data risks.
A New Season NFL Football season is upon us. And while I get to spend several hours watching my favorite team, my colleagues at Zebra MotionworksTM are revving up their analysis and insights as "The Official On-Field Player-Tracking Provider" of the NFL. As a fan, I'm amazed by all the information from tracking technology. Besides being cool, it captures data points that weren't even possible before and provides detailed views of players' health and performance.
We are always looking for ways to improve our products and processes at RapidSpike. We’ve recently completed an upgrade to our Google Lighthouse service software to Google’s latest version 9.6.7. This required us to almost entirely rearchitect how we run the tests, which allowed us to take advantage of the latest AWS technologies. This blog post explains what this change required.
We all know that observability is a must-have for operating systems in production. But we often neglect our own backyard — our software release process. We noticed we made that mistake here at Logz.io. We were wasting time and energy in handling failures in the CI/CD pipeline, and made our Developer-on-Duty (DoD) shifts tedious. That’s why it’s critical to incorporate your observability practices into your CI/CD pipeline.
Like I’ve mentioned in my last blog post, we use GitLab pipelines for packaging. We have a lot of software, like Icinga, Icingaweb and its various modules, which we want to build across multiple different operating systems. This results in a huge number of jobs and pipelines, doing very similar stuff. We have a lot of code repetition, and this is bad – code repetition means higher code maintenance , and it invites bugs.
Imagine being lost in a new place, and your maps don't help much. That sounds frustrating, right? Yet, it's precisely how your website visitors feel if you don't have functional website architecture to guide them through your content. Website architecture is the mind map that guides your visitors and search engines through the content on your website.
