2,495 karma · joined February 8, 2012
In that config under GPU benchmarking for ~10 mins, the 4090 runs at about 70°C for the GPU and 80°C for the VRAM
Although the 5800X3D technically has the same TDP, it seems that it pulls a lot less power for typical use, and is doing nicely with the Alpenföhn Black Ridge
https://formdworks.com / https://www.reddit.com/r/FormD/
I have the old T1 v1.1 (slightly smaller at 9.5L) - my current build has a 4090 FE & 5800X3D in it, all air cooled with excellent temps.
There's a particular YouTuber who does a lot of reviewing of SFF cases: https://www.youtube.com/watch?v=dTwie1pxuro
Just build and deploy everything on every merge. Compute is fairly cheap, and if running in parallel, it doesn't have to take long.
You can also take it a step further and have "mono" binaries/container images, where you specify the service to execute as the first argument.
I've been doing this for about 5 years now, having a single output artifact for each language being used. It works great.
If you're careful about your optimisations, you can go from hitting the merge button to having 100+ services deployed on production in about 60 seconds
Arguably it's a bit of an extremist approach, but if you have a situation where technically you're deploying thousands of times a day, you get pretty good at making the process reliable and robust
It also rewrites queries to make use of any materialized views you have, if it would make the query more efficient without affecting the results (so covers some use cases which indices would cover)
https://cloud.google.com/bigquery/docs/materialized-views-in...
Facebook: https://www.facebook.com/.well-known/openid-configuration
It's not really reporting in the visualisation or "send a PDF to a human" sense
I think we'll soon be left with the only remaining imperial bits being speed, long distances, and pints of beer - none of which seem likely to go away any time soon
We had a situation where one of our updates was rejected because they didn't like the app listing description (which has nothing to do with the update). The next update we pushed, we didn't change the listing metadata, and then it was accepted.
Always quite infuriating to work with Google Play.
The App Store is strict, but we've found it _far_ more consistent on applying the rules, and also dramatically faster to accept updates (usually accepts updates within about 6 hours, vs up to a week for Google Play).
But I remember really struggling to get my head around Obj-C syntax - I was trying to learn iOS development, but I hadn't been exposed to atypical syntax before, so it was completely tripping me up.
I left it a couple of years and eventually came back to it. At some point, I came across this page, and it finally made sense: http://cocoadevcentral.com/d/learn_objectivec/
Assuming you're using universal app links, if they open it on a device with the app installed, it'll go straight there. If not, it'll show the QR code and the user can just scan that with their default camera app on the device they're trying to use.
In those kinds of cases, cable management and space/size tolerances can be very difficult - swapping four connectors for one makes a big difference
These seem _dramatically_ cheaper than I expected. In my mind, I was thinking more like 3-5x this, though that was incl VAT/tax
GitHub Pages originally didn't support SSL on custom domains, so people would often put Cloudflare in front of it.
Now GHP does support SSL on custom domains, so Cloudflare is no longer needed, but obviously a lot of sites still exist with the original setup.