Comment on Intel's Meteor Lake CPUs are slower at single-core work than previous-gen models — new benchmarks show IPC regressions vs Raptor Lake

• vext01@lemmy.sdf.org ⁨5⁩ ⁨months⁩ ago

  Exactly.

  Also every time I’ve used async stuff, I’ve pined for proper threads. Continuation spaghetti isn’t my bag.

  source

  • kunaltyagi@programming.dev ⁨5⁩ ⁨months⁩ ago

    Which language? Usually there’s a thread pool where multiple tasks are run in parallel. CPython is a special case due to gil, but we have pypy which has actual parallelism

    source

    • vext01@lemmy.sdf.org ⁨5⁩ ⁨months⁩ ago

      I’ve only ever used it in those lua microcontrollers and in Rust with the async keyword.

      In lua I doubt they use proper threading due to the GIL. Rust probably can do async with threads, but it just wasn’t fun to work with.

      source

      • kunaltyagi@programming.dev ⁨5⁩ ⁨months⁩ ago

        Tokio has support for multiple threaded async in rust. As for micro controller, I don’t think you can have multiple threads in flight anyways, so that’s the best you’ll get

        source
• mihies@kbin.social ⁨5⁩ ⁨months⁩ ago

  Wait, wat? Looking at first sentence. Also async != multi threading.

  source
• GnomeKat@lemmy.blahaj.zone ⁨5⁩ ⁨months⁩ ago

  My goto for easy multi threading is lock free queues. Generate work on one thread and queue it up for another thread to process. Easy message passing and stuff like that. It doesn’t solve everything but it can do a lot if you are creative with them. As long as you maintain a single thread ownership of memory and just pass it around the threads via message passing on queues, everything just sorta works out.

  source

  • CrayonRosary@lemmy.world ⁨5⁩ ⁨months⁩ ago

    Don’t use goto.

    source
• brian@programming.dev ⁨5⁩ ⁨months⁩ ago

  A lot of languages have an asunc/await facade for tasks run on a background thread for result (c#, clj, py, etc), but it’s certainly not the default anywhere, and go most goroutines(?)/other csp implementations are probably going to be yielding for some io most of the time at the bottom anyway

  source

  • qqq@lemmy.world ⁨5⁩ ⁨months⁩ ago

    Yes I’m mostly familiar with this in Kotlin. Sometimes this is kinda a footgun because you’re writing multi threaded code without explicitly doing so.

    source