wengo314

if one could boostrap tcc with it, then it might be a viable tool.

jemalloc saved my icinga2 installation that kept exploding in memory usage, when i (and agents from sub-zones) was hammering its api

when i preloaded jemalloc , memory remained at significantly lower levels, and - more importantly - it was stable.

there seems to be no single correct solution to memory allocation, depending on the workload

you know, i don't think saying "got it right" is correct here.

Because if you are presenting an option of walking to a car wash as a valid choice, it suggests you just want to get there, and not wash your car.

Just like walking/driving to an airport doesn't necessarily mean you're going there to catch a flight (although it's a common reason). might as well be picking someone up. or working there.

i hope that whoever caused all those bugs doesn't move later into developing Azure.

(part of me actually wishes it would happen, ngl).

seems like a common occurence in the region, although the virus is highly contagious and very deadly.

i wish we instead dropped js for something vastly more sane.

maybe instead of HL3 they will deliver linux on the desktop for the masses.

because that's the foreseeable trajectory at this point

what a trip down memory lane.

for some extra nostalgia, check out "one finger death punch 2" game (and its prequel). i bet it's sort of an homage to those animations.

reject outright. ask to split it into reasonable chain of changesets.

this looks like maintenance nightmare going forward, but i could be wrong.

If you are stuck on specific pg version for a while, maybe it's worth it.

vibe coding could not have come at a worse moment.

true, i saw a thread recently on reddit where guy hand-tuned compilation flags and did pgo profiling for a video encoder app that he uses on video encode farm.

In his case, even a gain of ~20% was significant. It calculated into extra bandwidth to encode a few thousand more video files per year.

"Make one Ubuntu package 90% faster by rebuilding it and switching the memory allocator"

i wish i could slap people in the face over standard tcp/ip for clickbait. it was ONE package and some gains were not realized by recompilation.

i have to give it to him, i have preloaded jemalloc to one program to swap malloc implementation and results have been very pleasant. not in terms of performance (did not measure) but in stabilizing said application's memory usage. it actually fixed a problem that appeared to be a memory leak, but probably wasn't fault of the app itself (likely memory fragmentation with standard malloc)

* "if they want Adobe to be successful".

i wonder how this all win play out in the end.