How we ended up rewriting NuGet Restore in .NET 9 - .NET Blog
https://devblogs.microsoft.com/dotnet/rewriting-nuget-restore-in-dotnet-9/
How we ended up rewriting NuGet Restore in .NET 9 - .NET Blog
https://devblogs.microsoft.com/dotnet/rewriting-nuget-restore-in-dotnet-9/
https://www.europesays.com/de/33587/ Wie AT&S, Bawag, Lenzing, OMV, CA Immo und CPI Europe AG für Gesprächsstoff im ATX sorgten #Aktie #AktuelleNachrichten #AktuelleNews #AT&S #ATX: #Bawag #BG #CA #CAI #CPI #EU #Europa #EuropäischeUnion #Europe #EuropeanUnion #Headlines #Immo #Lenzing #LNZ #Nachrichten #News #OMV #Perf. #Schlagzeilen #SK #Symbol
... so, the final lesson here is that too many abstractions can impede the implementation's performance! many software abstractions introduce computational overhead, if they are not *very* carefully tailored to the application at hand. for something like mobile gaming on low-power devices, you need to treat each byte of processing energy with a high level of respect. that is what Vizflow was designed for #performance #perf #software #engineering #science #visualization #dataScience #art
the biggest question was: "can HTML5 games perform well on mobile?" and the answer for a while was "¯\_(ツ)_/¯"...
well, as someone who feels that visualizations and games are ultimately the exact same thing, and who likes both a lot, i wanted to try to answer this question for myself!
so, i set out to make some games using D3. That effort ended up failing, due to #performance (#perf) reasons, but it inspired me to make Vizflow :)
ES6 is partially based on CoffeeScript
anyway, a thing that this #dsl is: slow! on every frame it recompiles the layout. granted, the layout is simple. still it should be possible to compile it all to a thunk, and only recompile on edit...
that's the "editable ui" saga, anyway. and i'm not sure at all whether the dsl is the bottleneck, but once i add like 40 tracks and 40 scenes the rendering drops to <10FPS
so, #cargoflamegraph it is... #perf #profiler #flamegraph
If you use #linux #perf on #rust binaries, I highly recommend you check this out:
* https://github.com/torvalds/linux/commit/c3f8644c21df9b7db97eb70e08e2826368aaafa0
For a decently sized binary (just one!) we observed the following resource consumption on v6.6 and Debian Bookworm:
FBSD 14.x Kernel Build
81 seconds to compile a copy of GENERIC_KCSAN kernel on GhostBSD 24.10 (FreeBSD 14.1 base).
That's generally acceptable performance for an often silent Micro-ATX workstation (EPYC 4564P 16C/32T, 4.5GHz, 128/ECC, MB: H13SAE-MF). Potential improvements abound, sort of, given two requirements:
1. Low-dB acoustics, not "pitperf maxxing*"
2. Usage for mid-level Ai/ML on VMs for LLMs
What could be improved?
a) Upgrade GPU: 2x A4000 →Ada Gen
b) Upgrade NVMe: 2x M.2 PCIe Gen4 → Gen5
c) Swap 4x 32GB ECC → 4x 48GB ECC
d) Swap 4x DDR5-4800 → DDR5-5200
Cost/Benefit on those potential upgrades?
a) Cost = $$$, Benefit = ~10-25% vector perf
b) Cost = $, Benefit = ~1.5x I/O perf
c) Cost = $$, Benefit = 128GB → 192GB
d) Cost = $$$, Benefit = not a big deal
* PiT-Perf == Point In Time Performance
* Maxxing == Engaging in Applied Maximalism
Is there any good performance analysis out there comparing an inline `<style>` tag vs a render-blocking `<link>` when using HTTP/2 or 3?
I feel like making a separate request is bad, but I wonder if connection reuse solves that problem? What is the actual performance delta there?
…The
“Let’s load a progress bar so we can take over 30 seconds to compile and render a 250 row pseudo-table and tell ourselves that this is #perf ormant”
…guide to React-ing to requests
- - -
The
“Let’s set targets for ‘net zero’ that are beyond the current parliament and tell ourselves we are world leaders”
…guide to reacting to scientific findings
Pro tip:
You will be better off if you learn Perf and it is a wonderful tool. Learn it for your own enhancement's sake. If you are into low-level stuff and discovery.
cc:Arnaldo Carvalho de Melo -----> Maintainer of this tool
#linuxkernel #tool #perf #opensource #operatingsystem #PMU
Here to start with: https://perf.wiki.kernel.org/index.php/Tutorial
Pro tip:
You will be better off if you learn Perf and it is a wonderful tool. Learn it for your own enhancement's sake. If you are into low-level stuff and discovery.
cc:Arnaldo Carvalho de Melo -----> Maintainer of this tool
#linuxkernel #tool #perf #opensource #operatingsystem #PMU
Here to start with: https://perf.wiki.kernel.org/index.php/Tutorial
Does anyone have any good #linux or #bsd resources for explaining the nitty gritty details of how #perf tends suffers under max load due to timing windows being missed, tasks needing to be retried, etc? I'm thinking about process stalls due to higher iowait, memory allocation pressure leading to inefficient paging, disk command queue saturation leading to inefficient process wake-ups, etc. Conference slides or recordings would be great. Blog posts too.
Wait Operation Timeout when Wait Operation Timeout when monitoring App Pool .NET v4.5 Classic (PerfCounter IIS Application Pool) in PRTG?
#iis #webservers #windows #prtg #monitoring #perf #performance #apppool #appool #perfcounter #timeout #observability
omg, how do I properly profile a #rust programme that uses #rayon?
Rayon is *fantastic* for data parallelization, but when I try to use `perf(1)` in Linux, and open the results with (e.g.) `hotspot(1)` it's all just totally full of a million calls to `rayon::…`. Is there a way to collapse them all down?
Measuring Unikernel Cold Boot Time with Perf
https://nanovms.com/dev/tutorials/measuring-unikernel-cold-boot-time-with-perf
#ycombinator #perf #unikernel #cold_boot_time #wasm #TTFB #serverless