Shadow

Infrastructure nerd, gamer, and Lemmy.ca maintainer

  • 91 Posts
  • 1.55K Comments
Joined 2 years ago
cake
Cake day: June 22nd, 2023

help-circle
  • At the end of 2024, a Silicon Valley team that included researchers from Stripe, Anthropic, Tesla, and elsewhere produced a report showing that solar microgrids are by far the fastest way to build the power that data centers need. “Estimated time to operation for a large off-grid solar microgrid could be around 2 years (1-2 years for site acquisition and permitting plus 1-2 years for site buildout), though there’s no obvious reason why this couldn’t be done faster by very motivated and competent builders,” the report states. That’s because essentially all you have to do is put up a bunch of solar panels and some batteries and run a wire to your data center—not build a huge centralized power plant and connect it to the grid. The report continues, “Off-grid solar microgrids offer a fast path to power AI datacenters at enormous scale. The tech is mature, the suitable parcels of land in the US Southwest are known, and this solution is likely faster than most, if not all, alternatives.”

    I like this.





  • And memtest was booted off usb, not run in Linux or anything weird?

    That’s really odd. I’d definitely expect windows to crash, and it seems odd that it wouldn’t if both your sticks are failing when running on their own.

    I wonder if you actually have a mobo / CPU issue that windows can handle. Getting new ram seems like the logical next step though.




  • ShadowMAtoLemmy.ca Support / QuestionsTime outs
    link
    fedilink
    arrow-up
    2
    ·
    1 day ago

    I suspect something might be funky with your account, rather than the network / apps. The timeout message is a lie, you’re really getting 400 / 499 errors that seem to be related to this lemmy error message:

    2025-01-20T17:30:03.366014Z  WARN Error encountered while processing the incoming HTTP request: lemmy_server::root_span_builder: NotAModOrAdmin: NotAModOrAdmin
       0: lemmy_api_common::utils::check_community_mod_of_any_or_admin_action
                 at crates/api_common/src/utils.rs:102
       1: lemmy_api::local_user::report_count::report_count
    

    and:

    2025-01-20T20:39:43.202677Z  WARN Error encountered while processing the incoming HTTP request: lemmy_server::root_span_builder: CouldntFindPerson: Record not found
       0: lemmy_apub::fetcher::resolve_actor_identifier
                 at crates/apub/src/fetcher/mod.rs:22
       1: lemmy_apub::api::read_person::read_person
    

    I wonder if it could be a bug related to the unicode name you’ve got going on. Did you set that recently, or has it been like that since day 1?

    I just restarted all of our docker containers, see if that helps? If not, try setting a normal name and confirm if that changes things?










  • Compute no, but memory yes. Lemmy is actually pretty lean and efficient, but 32gb is a bit tight for a few instances of it as well as postgres. We run multiple instances to reduce the impact when one stutters (not uncommon).

    Upgrading to 64gb probably would have let us scale for the next year on the existing box, but I had this totally overkill hardware so might as well use it!