# measurements Published articles for measurements. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## pgAssistant 3.8.0 : continuous improvement loop for Postgres DevFeed: [pgAssistant 3.8.0 : continuous improvement loop for Postgres]() Original publisher: [Read original article]() Author: Pgassistant Dev Team Published: 2026-09-16T00:00:00Z Content type: release Language: en Sources: [PostgreSQL news]() Topics: [PostgreSQL](), [Monitoring](), [recommendations](), [configuration](), [real-time]() Tags: [configuration](), [measurements](), [monitoring](), [postgres](), [postgresql](), [real-time](), [recommendations](), [release]() ### AI overview pgAssistant 3.8.0 expands the PostgreSQL analysis and tuning tool into a continuous improvement platform. It adds historical workload and environment measurements, compares consecutive collections, tracks recommendations and configuration changes, and helps teams measure changes while distinguishing correlation from causation. ### Source excerpt With this release, pgAssistant is evolving beyond PostgreSQL analysis and tuning to become a continuous PostgreSQL improvement platform. The new positioning is built around a continuous improvement loop: Observe -> Diagnose -> Prioritize -> Plan -> Implement -> Collect again -> Measure pgAssistant already helped identify what should be improved and turn recommendations into a prioritized Executive Plan with clear DEV and OPS ownership. Combined with pgAssistant Collector, version 3.8.0 goes further by adding historical workload and environment measurements. The objective is to answer four essential questions: What should we improve? What did we decide to do? What did we actually change? What was the result? Workload Insights compares consecutive collections and highlights: new and no-longer-detected recommendations; changes to the PostgreSQL version and configuration; workload evolution by statement type; changes in execution time and call volume; the queries with the greatest impact on the overall workload. The ambition is to correlate the application of pgAssistant recommendations and the Executive Plan with observed performance changes. Correlation is not causation, and a recommendation that is no longer detected does not necessarily prove that it was implemented. pgAssistant keeps these distinctions explicit while bringing the relevant evidence together in one place. pgAssistant is not intended to replace real-time monitoring. Monitoring shows what is happening now; pgAssistant helps teams decide what to improve next, organize the remediation work, and measure what changed afterwards. From recommendations to action--and from action to measurable evidence. pgAssistant 3.8.0: https://github.com/beh74/pgassistant-community pgAssistant Collector: https://github.com/beh74/pgassistant-collector pgAssistant Grafana : https://github.com/beh74/pgassistant-grafana ## One or two nameservers? DevFeed: [One or two nameservers?]() Original publisher: [Read original article]() Author: Geoff Huston Published: 2026-09-15T06:01:49Z Content type: article Language: en Sources: [APNIC Blog]() Topics: [Internet](), [Query (disambiguation)](), [Server](), [Caching]() Tags: [2026](), [africa](), [article](), [china](), [dns](), [europe](), [experiment](), [india](), [internet](), [ipv4](), [ipv6](), [measurement](), [measurements](), [recursive-resolver](), [repeat](), [responses](), [server](), [tech-matters]() ### AI overview This article reports an experiment testing whether serving a DNS zone with two authoritative dual-stack nameservers changes repeated queries. Compared with one nameserver, two nameservers increased the single-query completion rate from 58% to 71% and reduced the average queries per test from 3.43 to 2.57. ### Source excerpt Do multiple dual-stack nameservers increase or decrease repeat DNS queries? The results of this experiment were a complete surprise. ## The Internet's New Edge Builders DevFeed: [The Internet's New Edge Builders]() Original publisher: [Read original article]() Author: Arman Obosyan Published: 2026-09-08T06:55:03Z Content type: article Language: en Sources: [RIPE Labs]() Topics: [Internet](), [Cloud](), [Networks](), [Network](), [amazon](), [Google](), [Meta](), [Microsoft]() Tags: [amazon](), [architecture](), [article](), [atlas](), [cdn](), [cloud](), [google](), [infrastructure](), [internet](), [internet-infrastructure](), [measurements](), [meta](), [microsoft](), [network](), [networks](), [peering](), [research](), [systems]() ### AI overview The article examines how content and cloud platforms are moving from operating private backbones toward controlling delivery infrastructure closer to users. It discusses the changing role of traditional CDNs, public measurements of international bandwidth, private interconnection and caches within access networks, and what Google and Meta deployments reveal about network operators. ### Source excerpt After building private backbones, content and cloud platforms are now moving closer to users. In doing so, they are taking on delivery roles once associated mainly with independent CDNs. ## Micron 6600 ION 245TB: Swap the Hard Drives, Power an NVL72 for Free DevFeed: [Micron 6600 ION 245TB: Swap the Hard Drives, Power an NVL72 for Free]() Original publisher: [Read original article]() Author: Brian Beeler Published: 2026-09-03T17:00:39Z Content type: article Language: en Sources: [StorageReview.com]() Topics: [Benchmark](), [benchmarking](), [datacenter](), [GB200](), [GPU](), [Server](), [dell]() Tags: [benchmark](), [compute](), [data-center](), [dell](), [efficiency](), [enterprise](), [gb200](), [gpu](), [hdd](), [measurements](), [nvl72](), [performance](), [servers](), [ssd](), [storage]() ### AI overview This article evaluates replacing eight 30TB nearline HDDs with one 245TB Micron 6600 ION SSD. Its measurements indicate lower power consumption, substantially higher read efficiency, and a reduction from 22 racks of HDD storage to six racks of flash at exabyte scale, potentially freeing enough power for a GB200 NVL72. ### Source excerpt For two decades, the SSD-versus-HDD conversation ended the same way: flash wins on performance, disk wins on price per terabyte, and the size of that price gap settled the argument in favor of bulk storage. As storage technology has matured and AI has taken over, that framing is clearly out of date. The largest data The post Micron 6600 ION 245TB: Swap the Hard Drives, Power an NVL72 for Free appeared first on StorageReview.com. ## When Traceroutes Lie: How TTL Jumps Can Give Us a False Impression of the Internet's Topology DevFeed: [When Traceroutes Lie: How TTL Jumps Can Give Us a False Impression of the Internet's Topology]() Original publisher: [Read original article]() Author: Sebastian Kappes Published: 2026-09-03T12:03:26Z Content type: article Language: en Sources: [RIPE Labs]() Topics: [Internet](), [Networks](), [debugging]() Tags: [atlas](), [competition](), [debugging](), [internet](), [measurements](), [networks](), [research](), [router]() ### AI overview This article explains how routers that rewrite or fail to decrement TTL values can cause traceroute to omit entire networks and create a false impression of Internet topology. It describes the normal traceroute mechanism and measurements using RIPE Atlas probes to investigate the behavior. ### Source excerpt Traceroute is a powerful tool for uncovering how packets travel across the Internet. However, as we recently discovered, some routers tamper with the TTL values in traceroute's probing packets, giving you a false view of how networks are actually interconnected. ## The IRR Landscape: What RPKI Can Replace DevFeed: [The IRR Landscape: What RPKI Can Replace]() Original publisher: [Read original article]() Author: Matthias Wichtlhuber Published: 2026-09-01T12:20:33Z Content type: article Language: en Sources: [RIPE Labs]() Topics: [BGP](), [Routing Security](), [Routing (disambiguation)](), [Databases](), [Internet]() Tags: [analysis](), [bgp](), [competition](), [data](), [database](), [ixps](), [measurements](), [overview](), [research](), [routing](), [routing-security](), [rpki](), [series]() ### AI overview This article analyzes which parts of the Internet Route Registry landscape can safely be replaced by RPKI using traffic and route-server data from AMS-IX and DE-CIX. It concludes that third-party ROUTE(6) objects can largely be phased out, while third-party AS-SETs remain important for BGP filter generation. ### Source excerpt In the third part of our IRR landscape series, we use traffic measurements from AMS-IX and DE-CIX to assess which parts of the IRR landscape can safely be replaced with RPKI. Third-party ROUTE(6) objects can largely be phased out, while third-party AS-SETs remain essential for BGP filter generation. ## Benchmarking vector indexes DevFeed: [Benchmarking vector indexes]() Original publisher: [Read original article]() Author: Evgeniy Patlan Published: 2026-08-27T13:35:32Z Content type: article Language: en Sources: [Blog - Percona]() Topics: [benchmarking](), [Ground truth / benchmark quality](), [Databases](), [ann](), [datasets](), [Sorting]() Tags: [ai-vector](), [ann](), [benchmark](), [benchmarking](), [benchmarks](), [blog](), [blog-post](), [data](), [database-performance](), [database-trends](), [databases](), [datasets](), [embeddings](), [index](), [measurements](), [model](), [open-source](), [percona](), [points](), [report](), [run](), [search](), [sorting](), [vector-search](), [vectorsearch]() ### AI overview This article explains how Percona's vector-bench measures vector indexes by building database engines from pinned versions, running them in identical containers with the same data and hardware, and comparing consistent measurements. It describes embeddings, exact search, approximate nearest neighbour search, and ground truth as the brute-force reference needed to evaluate index accuracy. ### Source excerpt Nearly every database has vector search now, and every one of them has a blog post with a big number in it. Almost none of those numbers can be checked, because the thing that makes them meaningful is usually missing. We built a vector-bench to stop guessing. You name the engines you want, build them ... Continued The post Benchmarking vector indexes appeared first on Percona. ## Two Providers, a Stubborn Plateau and a Very Long Tail: Email in the Tranco Top-1M DevFeed: [Two Providers, a Stubborn Plateau and a Very Long Tail: Email in the Tranco Top-1M]() Original publisher: [Read original article]() Author: Artem Berezin Published: 2026-07-30T11:49:26Z Content type: article Language: en Sources: [RIPE Labs]() Topics: [Time Series](), [microsoft 365](), [Resilience](), [Google](), [Microsoft](), [migration](), [Server](), [Internet](), [data](), [Software as a service](), [proofpoint]() Tags: [2026](), [authentication](), [competition](), [data](), [dns](), [google](), [measurements](), [microsoft](), [microsoft-365](), [migration](), [popular](), [resilience](), [saas](), [server](), [time-series]() ### AI overview A decade of DNS measurements across the Tranco top 1 million domains shows that email infrastructure is consolidating around Google Workspace and Microsoft 365. Self-hosted mail servers declined from 44.6% in 2016 to 22.4% in July 2026, while the two leading providers together handled 38.6% of measured domains. DMARC enforcement has plateaued, and a large long tail of infrastructure remains difficult to classify. The article frames this concentration as a resilience concern because outages, filtering changes, or policy decisions could affect a substantial part of the email ecosystem. ### Source excerpt Ten years of DNS measurements reveal three trends across the Internet's most popular domains: email continues to consolidate around two providers, DMARC enforcement has hit a plateau, and a surprisingly large long tail of infrastructure defies easy classification. ## Developer productivity insights platforms (DPIP) measure dashboards. Your DevEx problem is bigger Than that. DevFeed: [Developer productivity insights platforms (DPIP) measure dashboards. Your DevEx problem is bigger Than that.]() Original publisher: [Read original article]() Author: Zohar Einy Published: 2026-07-30T11:28:55Z Content type: opinion Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [code productivity](), [devex](), [dashboards](), [developer-productivity](), [Artificial Intelligence](), [DevOps](), [Platform Engineering](), [CI/CD](), [Large Language Model](), [Optimization](), [migration]() Tags: [agentic](), [ai](), [ci-cd](), [dashboards](), [developer-productivity](), [devex](), [devops](), [llm](), [measurements](), [metrics](), [migration](), [optimization](), [platform-engineering]() ### AI overview This developer article argues that Developer Productivity Insight Platforms (DPIP) should extend beyond measuring engineering time, resources, effectiveness, and delivery progress. It says dashboards and metrics are insufficient without workflows and self-service actions that help developers resolve identified problems. The article also highlights platform convergence, CI/CD integrations, agentic solutions, LLM support, resource optimization, and data migration, arguing that enterprise engineering needs an end-to-end platform connecting insight to action. ### Source excerpt Gartner defines DPIP as solutions that provide software engineering leaders with data-driven insights into their teams' use of time, resources, operational effectiveness and progress on deliverables. ## Query Speed Insights from the Vercel CLI DevFeed: [Query Speed Insights from the Vercel CLI]() Original publisher: [Read original article]() Author: Ergün Erdoğmuş Published: 2026-06-29T08:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Command-line interface](), [Core Web Vitals](), [benchmarking](), [Web]() Tags: [cli](), [core-web-vitals](), [insights](), [measurements](), [metrics](), [performance](), [performance-metrics](), [vercel](), [web]() ### AI overview Vercel CLI can now query Speed Insights datapoints, including Core Web Vitals and other page performance metrics collected from real user traffic. The feature supports investigating regressions and comparing performance across pages, regions, and device types. ### Source excerpt You can now query Speed Insights datapoints directly through the Vercel CLI. Using the vercel metrics command, you can pull core Web Vitals (LCP, INP, CLS) and other page performance metrics (FCP, TTFB) based on client-side measurements from real user traffic. By providing a coding agent access to the CLI, an agent can answer questions such as: Which pages' INP have regressed since last week? How is the perceived speed of my home page in Asia? Compare the CLS of the dashboard between mobile and desktop. For more details on how to use the CLI command and a complete list of supported metrics, dimensions, filters, and query options, explore the documentation. Read more ## 5 things designers need to know for a smooth handoff DevFeed: [5 things designers need to know for a smooth handoff]() Original publisher: [Read original article]() Author: Lauren Byrne Published: 2024-02-14T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [pull-requests]() Tags: [collaboration](), [communication](), [design](), [figma](), [measurements](), [platforms](), [process]() ### AI overview The article presents design handoff as an ongoing process of communication and collaboration rather than a single event. It shares guidance for improving handoff, including using annotations in Figma Dev Mode to communicate design intent, specifications, measurements, notes, component usage, interactions, and platform-specific differences. ### Source excerpt Handoff is a process, not a moment. So how do you streamline handoff when it's a constant stream of WIP designs, communication, and collaboration? Designer Advocate Lauren Andres shares her tips. ## The Importance of Using a Composite Metric to Measure Performance DevFeed: [The Importance of Using a Composite Metric to Measure Performance]() Original publisher: [Read original article]() Author: Ben Cripps Published: 2024-01-31T21:57:58Z Content type: article Language: en Sources: [Indeed]() Topics: [performance measurements](), [client](), [Usability](), [JavaScript](), [Google Analytics]() Tags: [engineering](), [google-analytics](), [javascript](), [measurements](), [performance](), [performance-measurements](), [usability]() ### AI overview Indeed examines the limitations of relying on a single client-side performance metric, including incomplete coverage of third-party content and poor alignment with actual usability. It suggests that a composite metric can better measure users' experience. ### Source excerpt In the past, Indeed has used a variety of metrics to evaluate our client-side performance, but we've tended to focus on one at a time. Traditionally, we chose a single performance metric and used it as the measuring stick for whether we were improving or degrading the user experience. This made it simple to track [...] ## Checking compressed size of Docker image DevFeed: [Checking compressed size of Docker image]() Original publisher: [Read original article]() Author: Tom Published: 2024-01-24T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [Docker Image](), [Docker](), [Containers](), [Bash](), [Jenkins]() Tags: [bash](), [bash-function-for-docker](), [compressed-docker-image](), [containers](), [docker](), [docker-image](), [docker-image-metrics](), [docker-image-size](), [docker-optimization](), [docker-performance](), [how-to](), [linux](), [measurements]() ### AI overview The article explains how to use Docker image compressed size as a development metric for estimating download-time impact, while comparing it with uncompressed size to approximate extraction and startup-time impact. It presents a Bash function to simplify the measurements. ### Source excerpt Learn how to check the compressed size of Docker images to optimize download and startup times, using a simple bash function for accurate measurements. ## 2023 Web Framework Performance Report DevFeed: [2023 Web Framework Performance Report]() Original publisher: [Read original article]() Author: Fred Schott Published: 2023-03-07T00:00:00Z Content type: article Language: en Sources: [The Astro Blog]() Topics: [Frameworks](), [Core Web Vitals](), [Web](), [data](), [Astro](), [gatsby](), [Next.js](), [Nuxt.js](), [Remix](), [WordPress]() Tags: [astro](), [core-web-vitals](), [framework](), [measurement](), [measurements](), [next-js](), [nuxt](), [performance](), [remix](), [report](), [web]() ### AI overview This report examines how Astro, Gatsby, Next.js, Nuxt, Remix, SvelteKit, and, where possible, WordPress relate to real-world web performance and user experience in 2023. It uses publicly available data from the Chrome User Experience Report, HTTP Archive, and Core Web Vitals Technology Report, rather than performance measurements collected directly by Astro. ### Source excerpt A look at how different web frameworks perform in the real world in 2023. Based on real-world, production data from HTTP Archive and Google Chrome. ## Compose by example: Intrinsics DevFeed: [Compose by example: Intrinsics]() Original publisher: [Read original article]() Author: James Shvarts Published: 2022-11-05T22:25:24Z Content type: tutorial Language: en Sources: [Android Blog - Mobile Dev Notes]() Topics: [Compose](), [Jetpack Compose]() Tags: [compose](), [jetpack-compose](), [layout](), [measurements]() ### AI overview A Jetpack Compose example showing how intrinsic measurements and IntrinsicSize can make a middle column match the height of the tallest column in a row. ### Source excerpt Example of using IntrinsicSize in Jetpack Compose ## Histogram vs eCDF DevFeed: [Histogram vs eCDF]() Original publisher: [Read original article]() Author: Marc Brooker Published: 2022-09-02T00:00:00Z Content type: article Language: en Sources: [Marc Brooker's Blog](), [Marc Brooker's Blog]() Topics: [Statistics](), [Latency](), [Caching](), [Low Latency](), [systems](), [data](), [Databases]() Tags: [cache](), [data](), [databases](), [latency](), [low-latency](), [measurements](), [statistics](), [systems]() ### AI overview The article compares histograms with empirical cumulative distribution functions (eCDFs) for presenting latency and other measured data. It argues that eCDFs make multimodal distributions, percentile values, cache hit rates, and tail behavior easier to interpret and inspect. ### Source excerpt Histogram vs eCDF Accumulation is a fun word. Histograms are a rightfully popular way to present data like latency, throughput, object size, and so on. Histograms avoid some of the difficulties of picking a summary statistic, or group of statistics, which is hard to do right. I think, though, that there's nearly always a better choice than histograms: the empirical cumulative distribution function (eCDF). To understand why, let's look at an example, starting with the histogram1. This latency distribution is very strongly bimodal. It's the kind of thing you might expect from a two-tiered cache: a local tier with very low latency, and a remote tier with latency in the 2 to 3ms range. Super common in systems and databases. The histogram illustrates that bimodality very well. It's easy to see that the second mode is somewhere around 2.5ms. The next two questions on my mind would be: how much do these two spikes contribute? and where is the first spike? In histogram form, its hard to answer these questions. The first we'd need to answer by doing some mental area-under-the-curve estimation, and the second is obscured by bucketing. Here's the same data in eCDF form. You can think of it as the histogram summed up, or integrated, or accumulated2. The first thing you may notice is how easy it has become to see the relative contribution of our first and second mode. The first mode contributes around 70% of measurements. If this is a cache system, we immediately know that our cache hit rate is around 70%. We also know that the 65th percentile is very low, and the 75th is very high. In fact, we can read these percentile3 values right off the graph by finding the 0.65 and 0.75 points on the Y axis, moving right until we hit the curve, and reading their value off the X axis. Magic! The second question, about the location of the first spike, can be answered by zooming in. That works because the eCDF, unlike the histogram, doesn't require bucketing, so we can zoom around in X and Y ## Dutch Solar Power Figures Are Estimates Based on the Entrance Model DevFeed: [Dutch Solar Power Figures Are Estimates Based on the Entrance Model]() Original publisher: [Read original article]() Published: 2022-03-27T08:47:53Z Content type: opinion Language: en Sources: [Bert Hubert's writings]() Topics: [data](), [realtime]() Tags: [data](), [energy](), [generate](), [graphs](), [interface](), [live](), [measurements](), [model](), [solar]() ### AI overview The article examines Dutch electricity data submitted to ENTSO-E and explains that the Netherlands does not report solar generation directly. Reported real-time solar figures appear to be estimates produced by the Entrance model, based on parameters such as solar-field data, temperature, irradiation intensity, and panel orientation. ### Source excerpt As part of my coping mechanisms, I like to make graphs of important things I worry about. Recently with the Russia-inflicted horrors in Ukraine, I've been looking at the torrent of Russian gas being bought by Europe. This turned into a live plot that shows just how much money we are sending to Russia. In that post, I also dwell on how we are using that gas to heat our houses and generate electricity. ## Dodging a bullet: Ethereum State Problems DevFeed: [Dodging a bullet: Ethereum State Problems]() Original publisher: [Read original article]() Author: Martin Holst Swende; Peter Szilagyi Published: 2021-05-18T00:00:00Z Content type: article Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Database](), [Security](), [Bug Bounty](), [Exploit]() Tags: [attacks](), [blog](), [blog-post](), [bug](), [bug-bounty](), [cryptographic](), [database](), [ethereum](), [exploit](), [hash](), [measurements](), [security](), [state](), [upgrade]() ### AI overview This Ethereum blog post discloses a severe state-related threat that remained dangerous until the Berlin hardfork. It explains how the growth of Ethereum's patricia-merkle trie increases database lookups and disk operations, describes gas-cost increases introduced to mitigate denial-of-service risks, and discusses an exploit submitted to the Ethereum bug bounty. ### Source excerpt With this blog post, the intention is to officially disclose a severe threat against the Ethereum platform, which was a clear and present danger up until the Berlin hardfork.... ## Keeping Developers Happy with a Fast CI DevFeed: [Keeping Developers Happy with a Fast CI]() Original publisher: [Read original article]() Author: Christian Bruckmayer Published: 2021-02-24T15:44:31Z Content type: article Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [ci](), [Shopify](), [build times](), [Instrumentation](), [cloud-infrastructure](), [Git](), [Shell]() Tags: [agents](), [automated](), [build](), [build-times](), [ci](), [cloud](), [cloud-infrastructure](), [code](), [commands](), [developers](), [development](), [git](), [infrastructure](), [instrumentation](), [jobs](), [measurements](), [performance](), [speed](), [test](), [tests]() ### AI overview Shopify describes how its Test Infrastructure team improved the performance of its continuous integration system for a core monolith. By adding detailed instrumentation, analyzing build and job data, and using scalable CI infrastructure, the team reduced p95 CI time from about 45 minutes to 18 minutes while pursuing a goal of under 10 minutes. ### Source excerpt Slow CI systems are often responsible for making frustrated developers. Keeping these systems fast requires an ongoing effort. However, before jumping into implementing performance tweaks, it's important to set up a solid monitoring system. ## Review of the Uputronics GPS/RTC Raspberry Pi Expansion Board DevFeed: [Review of the Uputronics GPS/RTC Raspberry Pi Expansion Board]() Original publisher: [Read original article]() Published: 2020-07-09T11:38:00Z Content type: comparison Language: en Sources: [Bert Hubert's writings]() Topics: [Raspberry Pi](), [Hardware](), [Monitoring]() Tags: [configuration](), [gnss](), [measurements](), [pi-4](), [raspberry-pi](), [receiver](), [review](), [timing]() ### AI overview A review of Uputronics' GPS/RTC Raspberry Pi Expansion Board, tested with the galmon.eu GNSS monitoring project. The board uses a u-blox M8 timing receiver, provides raw GNSS and correlator data, and offers a stable clock signal. The review also covers antenna performance, Raspberry Pi 4 configuration, UART communication, and baud-rate considerations. ### Source excerpt Hi everyone, Disclaimer: this is a review of a free sample I got sent by Uputronics. I recently spotted on Twitter that Uputronics had launched a GPS/RTS Raspberry Pi Expansion Board, and that they were looking for worthy projects to test it. I thought our Galileo/GPS/BeiDou/GLONASS monitoring project galmon.eu might be worthy and Uputronics agreed. Relevant for our purposes, this is an actual 'timing receiver'. Any GNSS chip will get you a location, but some of them go the extra mile to also deliver a very stable clock signal. ## How to Find Device Metrics for Any Screen DevFeed: [How to Find Device Metrics for Any Screen]() Original publisher: [Read original article]() Published: 2020-05-19T13:00:00Z Content type: tutorial Language: en Sources: [Material.io - Material Design]() Topics: [screen]() Tags: [design](), [devices](), [how-to](), [measurements](), [screen]() ### AI overview A guide to finding device metrics and calculating measurements for design across different screens. ### Source excerpt Calculate the right measurements for design across devices ## A CEO's Experience During the COVID-19 Crisis -- Part III : Looking Ahead DevFeed: [A CEO's Experience During the COVID-19 Crisis -- Part III : Looking Ahead]() Original publisher: [Read original article]() Author: John Lee Published: 2020-03-07T00:00:00Z Content type: opinion Language: en Sources: [Blog on Developer Portal]() Topics: [Espressif](), [Statistics]() Tags: [blog](), [ceo-blog](), [covid](), [covid-19](), [esp-rainmaker](), [esp32](), [espressif](), [experience](), [future](), [japan](), [measurement](), [measurements](), [performance](), [statistics](), [us](), [work]() ### AI overview Espressif CEO Teo Swee Ann provides an update on how COVID-19 has affected the company and discusses the future. The article also reports preliminary results from a high-risk test chip, including improved performance and lower power consumption under limited conditions. ### Source excerpt The COVID-19 situation is developing rapidly, and the CEO of Espressif, Teo Swee Ann, gives a short update of the situation and some considerations of the future. The COVID-19 situation continues to unfold fast and globally. It has reached Europe, Japan, South Korea, and the United States, and on the minds of many is whether COVID-19's advance will be arrested by warmer weather or if a cure or vaccine will be found. ## test\_awsy\_lite: Android Mochitest Performance Testing with Perfherder DevFeed: [test\_awsy\_lite: Android Mochitest Performance Testing with Perfherder]() Original publisher: [Read original article]() Author: gbrown-mozilla Published: 2016-01-27T13:39:53Z Content type: article Language: en Sources: [Mozilla Automation]() Topics: [Android](), [Testing](), [Performance Testing](), [Mobile](), [Hardware]() Tags: [android](), [firefox-for-android](), [measurements](), [memory](), [mobile](), [mozilla](), [performance-testing](), [testing]() ### AI overview The article discusses test_awsy_lite.html, an Android-only mochitest-chrome test inspired by areweslimyet.com. It compares the approach with custom harnesses such as Talos, covering local debugging, Perfherder reporting, emulator limitations, runtime constraints, and the use of Resident memory measurements. ### Source excerpt Bug 1233220 added a new Android-only mochitest-chrome test called test_awsy_lite.html. Inspired by https://www.areweslimyet.com/mobile/, test_awsy_lite runs similar code and takes similar ... Continue reading -> ## Nim binary size from 160 KB to 150 Bytes DevFeed: [Nim binary size from 160 KB to 150 Bytes]() Original publisher: [Read original article]() Published: 2015-05-03T22:00:00Z Content type: tutorial Language: en Sources: [Dennis Felsing]() Topics: [Nim](), [Programming](), [Compiler](), [Linux]() Tags: [c](), [clang](), [compilation](), [compiler](), [gcc](), [glibc](), [linux](), [measurements](), [nim](), [x86]() ### AI overview This tutorial explores how to reduce the size of a simple Nim binary on Linux. It demonstrates builds using GCC and Clang, including a 6 KB binary, a 952-byte binary without the C standard library, and a 150-byte binary using a custom linker script and ELF header. ### Source excerpt The size of binaries in the Nim programming language seems to be a popular topic recently. Nim's slogan is expressive, efficient, elegant, so let's examine the efficient part in this post by exploring a few ways to reduce the size of a simple Nim Hello World binary on Linux. Along the way we will: Build a regular program into a 6 KB binary Disregard the C standard library and build a 952 byte binary Use a custom linker script and ELF header to build a 150 byte binary (1 byte smaller than in Rust) The full source code of this post can be found in its repository. All measurements are done on Linux x86-64 with GCC 5.1 and Clang 3.6.0. Using the C Standard Library echo "Hello!" By default Nim uses GCC as the backend C compiler on most platforms, and we dynamically link against glibc. We can try optimizing for speed and size, as well as strip unnecessary symbols after the compilation: Command (GCC backend) Binary Size nim c hello 160 KB nim -d:release c hello 61 KB nim -d:release --opt:size c hello 25 KB nim -d:release --opt:size c hello && strip -s hello 19 KB That's pretty nice and can be done with any Nim program to reduce binary size. Now let's try to get rid of glibc, at least temporarily (we will come back to a more permanent solution later). Instead of glibc we're now statically linking against musl libc: $ nim --gcc.exe:/usr/local/musl/bin/musl-gcc \ --gcc.linkerexe:/usr/local/musl/bin/musl-gcc \ -d:release --opt:size --passL:-static c hello $ strip -s hello 30 KB Update: The order of arguments to nim matters, --passL:-static has to be passed after setting the gcc exe so that it isn't overwritten. So that's a statically linked binary in 30 KB, which can be deployed without depending on any glibc version (or any other libraries)! What about using Clang instead of GCC by setting --cc:clang: Command (Clang backend) Binary Size nim --cc:clang c hello 168 KB nim --cc:clang -d:release c hello 33 KB nim --cc:clang -d:release --opt:size c hello 29 KB nim --cc:clang -d:re [Next page]()