So does anyone have a good guide on what I am actually looking at in the Sharkey dashboard?
-
@[email protected] @[email protected] @[email protected] I once tossed a comforter on my 25u server rack suffocating it so the temps would spike just to heat my room up a bit more when I took off the comforter because I knew it’d take a while for it to go back to its normal temperature range. This is because I am a completely normal individual
-
ash nova :neocat_flag_genderfluid:replied to Amber 🌸 last edited by
@[email protected] @[email protected] I'm running dedicated workers and MK_SERVER_ONLY nodes, but I haven't split those up into different API routes or anything like that if that's what you mean, they just do all the web traffic pretty much. Been meaning to separate out AP things from client web but I can't quite be bothered to write that much nginx conf rn and changing my own HTTP to HAProxy is more of a longer term project xD
-
@[email protected] @[email protected] @[email protected] it’s so funny to see idrac reporting 130°F exhaust temperatures. I didn’t believe it, so I put my hand behind my server and wew you’ll never guess this - it wasn’t kidding.
-
Amber 🌸replied to ash nova :neocat_flag_genderfluid: last edited by
@[email protected] @[email protected] you can go even further - you can separate the url preview by running an instance of summaly yourself and giving misskey the url. Same goes for the media proxy (which I still need to do because I was going to run it in a docker container with cpu limits so at max it can only max out a single core instead of taking everything else down) on top of using split instance config and using prefix+protocol routing within haproxy to separate api, websocket and federation traffic to their own nodes