The stock heatsink actually did a pretty good job. The server still idles at the same temp as it did with the stock, however, I expect the real gains to be when it is under full load it will stay within thermal margins to maintain all-core max boost clock of 2.9 GHz.
I spent 4 hours building a fucking query for the business team to do some analytics.
I get it working perfectly and one guy jumps on slack, on his phone, assuming that the query doesnât work and will return duplicates, by UUID.
I tried to explain the query to him. He didnât understand. I offered to hop on a call and explain it. He wasnât available.
Finally, I just gpgâd the results over, told him to look at this:
cat Result.csv | cut -d \, -f 1 | uniq -d
Iâve knocked over every conditional and he just says âitâs still not rightâ
How the fuck is it not right? Because I used subqueries the way he doesnât like? I returned the right data. I didnât lock the database. I didnât knock it over trying to process half a billion records.
Do you ever get that one guy who writes huge sequential queries? Because your database is on ridiculous NVMe storage and it can stream sequential scans at 6 GB/s and theyâre all like, âWhat!? It doesnât matter, it runs fast like it is.â
Accidentally got a barebones server on ebay thatâs incompatible with the E5v2 CPUs I already had to put in it, so now Iâm getting E5v3 CPUs too.
Sadly also incompatible with the 80GB of DDR3 reg ECC I ordered to go with the 16GB I already have, so now Iâm getting 128GB DDR4 reg ECC and that really hurts.
Anyone need some DDR3 server memory T_T
GitLab 13.0 is going to ship May 22nd and is going to be an exciting release. One of the main features I am excited about is the security scanning like how GitHub does it.
Iâve had luck buying directly from Unix Surplus. If theyâre not too busy, theyâll spec something custom for you and they readily have compatibility info on their units.