# scheduling Scheduling is the computing technique of determining which computational task, process, or thread runs on a processor and for how long when tasks compete for finite processing resources. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## libosmocore - libosmocore 1.14.1 released DevFeed: [libosmocore - libosmocore 1.14.1 released]() Original publisher: [Read original article]() Author: osmith Published: 2026-07-22T10:37:33Z Content type: release Language: en Sources: [Open Source Mobile Communications: News]() Topics: [changelog](), [IO](), [cpu](), [scheduling](), [make]() Tags: [2026](), [bug](), [changelog](), [cpu](), [io](), [issue](), [make](), [scheduling](), [tracker]() ### AI overview libosmocore 1.14.1 has been released with fixes to I/O queue handling, CPU scheduling initialization and platform-dependent scheduling support, utility issues, and a missing crypto header in the build configuration. ### Source excerpt Today we've released libosmocore 1.14.1. The changelog over 1.14.0 is as follows: libosmocore (1.14.1) unstable; urgency=medium [ Vadim Yanitskiy ] * osmo_io: iofd_txqueue_dequeue(): fix double next->io_len decrement [ Timur Davydov ] * vty: fix osmo_cpu_sched_vty_init() prototype * vty: make CPU scheduling optional based on platform support [ Oliver Smith ] * utils: fix typos * utils/gsmtap-logsend: close infile before exit [ Alexander Couzens ] * gsm/Makefile.am: add missing kdf/crypto.h -- Oliver Smith Wed, 22 Jul 2026 11:30:55 +0200 ## BSDCan 2026 Trip Report - ShengYi Hung DevFeed: [BSDCan 2026 Trip Report - ShengYi Hung]() Original publisher: [Read original article]() Author: Florine Kamdem Published: 2026-07-22T05:40:54Z Content type: article Language: en Sources: [FreeBSD Foundation]() Topics: [freebsd](), [scheduling](), [cpu](), [LLVM]() Tags: [blog](), [conference](), [developers](), [report]() ### AI overview A personal report on attending BSDCan 2026 in Ottawa, including DevSummit discussions about AI and project maintainability, FreeBSD development work, heterogeneous CPU scheduling, CPU power throttling, and Thread Local Storage. ### Source excerpt I'm really grateful to the FreeBSD Foundation for sponsoring my trip to BSDCan 2026 in Ottawa. The conference ran for four days -- two days of DevSummit, then two days of the main conference, with many interesting talks throughout. For me, it's mainly a chance to talk with developers I don't otherwise get to reach [...] The post BSDCan 2026 Trip Report - ShengYi Hung first appeared on FreeBSD Foundation. ## Managing an Engineer's Week as a Queueing System DevFeed: [Managing an Engineer's Week as a Queueing System]() Original publisher: [Read original article]() Author: hello@ankit-rana.com Published: 2026-03-15T00:00:00Z Content type: opinion Language: en Sources: [Ankit Rana | Mechanical Sympathy]() Topics: [queueing theory](), [scheduling](), [systems](), [Server]() Tags: [email](), [focus](), [minutes](), [notifications](), [productivity](), [queueing-theory](), [scheduling](), [servers](), [slack](), [software-engineering](), [system](), [time-management](), [work]() ### AI overview The article argues that software engineers' schedules behave like queueing systems: near-total utilization increases waiting time, while interruptions evict working context. It recommends maintaining schedule headroom, batching communications, and limiting work in progress. ### Source excerpt An engineer's week behaves like a queueing system: book yourself at 100% utilization and the wait time for anything new goes vertical, exactly as it does for a server. The fixes are the ones we already use in systems: keep headroom, coalesce interrupts instead of taking them one by one, cap work in progress because Little's law applies to you, and stop letting urgent-but-small tasks hold the lock while important work starves. ## Paper #196. The Sunk Carbon Fallacy: Rethinking Carbon Footprint Metrics for Effective Carbon-Aware Scheduling DevFeed: [Paper #196. The Sunk Carbon Fallacy: Rethinking Carbon Footprint Metrics for Effective Carbon-Aware Scheduling]() Original publisher: [Read original article]() Author: Aleksey Charapko Published: 2025-04-14T03:31:33Z Content type: article Language: en Sources: [Aleksey Charapko]() Topics: [scheduling](), [cpu](), [data centers](), [distributed-systems](), [Hardware](), [Computing](), [Benchmark]() Tags: [benchmark](), [carbon](), [computing](), [cpu](), [data-center](), [data-centers](), [distributed](), [distributed-systems](), [efficiency](), [emissions](), [hardware](), [reading-group](), [scheduling]() ### AI overview This article presents a reading-group discussion of a paper about carbon-aware scheduling. It explains how Software Carbon Intensity combines operational and embodied carbon, and argues that allocating embodied carbon to jobs can make scheduling decisions misleading, particularly in heterogeneous clusters. ### Source excerpt The last paper we covered in the Distributed Systems Reading group discussed CPUs, data centers, scheduling, and carbon emissions--we read "The Sunk Carbon Fallacy: Rethinking Carbon Footprint Metrics for Effective Carbon-Aware Scheduling." Below is my improvised presentation of this paper for the reading group. This paper was an educational read for me, as I learned [...] ## Explainable Linear Programs DevFeed: [Explainable Linear Programs]() Original publisher: [Read original article]() Published: 2025-02-07T05:24:38Z Content type: opinion Language: en Sources: [Jeremy Kun]() Topics: [Optimization](), [scheduling](), [Routing (disambiguation)](), [Large Language Model](), [Microsoft]() Tags: [google](), [large-language-models](), [microsoft](), [optimization](), [routing](), [scheduling](), [shortform]() ### AI overview The author describes a 2020 side project for explaining linear-programming solutions by interactively changing constraints or objectives, re-solving models, and aggregating differences using semantic metadata. The article connects this approach to a 2023 Microsoft paper that uses a large language model to translate natural-language queries into structured queries for supply-chain optimization. ### Source excerpt Back in 2020, when I worked in the supply chain side of Google, I had a fun and impactful side project related to human-level explanations of linear programs. A linear program is a mathematical model that defines some number of variables, linear constraints, and a linear objective function. When some variables are forced to be integer (ILPs), you can solve a lot of useful problems like scheduling, routing, and packing. That's basically how all supply chain optimization works. ## How Request processing has changed over the years DevFeed: [How Request processing has changed over the years]() Original publisher: [Read original article]() Published: 2025-02-03T00:00:00Z Content type: article Language: en Sources: [Gaurav Sarma's Blog]() Topics: [processing](), [Computer science](), [Concurrency](), [scheduling](), [Kernel](), [Processes](), [Ruby](), [Python]() Tags: [concurrency](), [cpu](), [kernel](), [process](), [processing](), [python](), [request](), [ruby](), [scheduling]() ### AI overview This article explains how web request processing works, distinguishing blocking and non-blocking tasks and introducing concepts such as CPU control, kernel behavior, and cooperative versus preemptive scheduling. It begins comparing request-processing architectures in the context of Ruby, Python, NodeJS, and Rails services. ### Source excerpt . [How Request Processing Has Changed Over the Years](how-request-processing-has-changed-over-the-years-cover... ## Using the Eisenhower Matrix to Manage Overwhelm DevFeed: [Using the Eisenhower Matrix to Manage Overwhelm]() Original publisher: [Read original article]() Author: Pedro Gil Carvalho Published: 2023-06-23T06:46:57Z Content type: opinion Language: en Sources: [Pedro Gil Carvalho]() Topics: [Matrix](), [systems](), [scheduling](), [meetings]() Tags: [delegation](), [matrix](), [meetings](), [scheduling](), [systems]() ### AI overview The author describes using management systems to handle recurring problems and reduce decision-making overhead. When competing priorities become overwhelming, they use the Eisenhower Matrix to classify tasks by urgency and importance, identify delegation opportunities, and review priorities on a Miro board. ### Source excerpt How the Eisenhower Matrix saves my day ## Come over for dinner DevFeed: [Come over for dinner]() Original publisher: [Read original article]() Author: Map Published: 2019-05-01T20:55:56Z Content type: opinion Language: en Sources: [Craig Kerstiens]() Topics: [hosting](), [trust](), [scheduling]() Tags: [hosting](), [philosophies](), [remote](), [scheduling](), [trust](), [work]() ### AI overview The author describes regularly inviting coworkers, former colleagues, and friends to dinner as an alternative to going out. They argue that shared meals build rapport and trust, support more effective teamwork, and can include remote workers and team members through planned scheduling and rotation. ### Source excerpt When I first moved to the Bay area I was fresh out of grad school. I was frequently heading out to dinner or to happy hour after work with colleagues. I was young and single, so why not of course. As time passed, marriage, kids, etc. the ability to go out for a quick drink or dinner was competing with various priorities. Dinner and drinks with co-workers was always a great time. It wasn't just about hanging out, it built rapport and trust which I found made me a more effective teammate and product manager. It was about 8 years ago that I started to implement a variation of heading out for dinner and drinks. I started inviting people over for dinner. I still do this regularly. Roughly once a week we end up hosting someone for dinner. Sometimes it is a single person, sometimes it is a group of people. Sometimes it is co-workers, sometimes former colleagues, often friends that don't work in tech. Growing up in the south it was common to have people over, I'd said we did that just as much as going out to dinner with folks. You'd get an invite to go to someone elses place and you'd show up with a bottle of wine or flowers in hand. Initially when I asked people in the Bay area over for dinner I'd get weird looks. Over? Like to your house? The reaction from folks at the end of the night was very often... that was really fun. Thanks for the invite, I can't remember the last time I just sat down at someones place, had a good meal, and conversation. Once I found early success with this I started implementing it pretty methodically. When remote workers were in town I'd make sure to place them at thet top of the list to come if the scheduling worked. Same when friends visit from out of town. I'd also try to regularly rotate through my teams and those that report to me. At one point when I had 22 engineers that I was leading product for I had to do a bit of juggling and stagger things a bit, groups of 4 folks or so at a time and each would be over about once every 6 months. I made