GitHub recently removed the Out of Band Garbage Collector (OOBGC) from its production environment, leading to a 10% reduction in CPU utilization across its machines, as well as a 25% decrease in average response times, although it resulted in increased average memory usage. The OOBGC was initially implemented to manage the "stop the world" pause times of Ruby's traditional garbage collector by running garbage collection after web requests were processed, but advancements in Ruby's garbage collector, including generational collection, incremental marking, and lazy sweeping, have improved its efficiency, rendering OOBGC less necessary. By eliminating OOBGC, GitHub observed significant CPU savings, which outweighed the increased memory usage, highlighting the importance of reassessing technological assumptions in light of ongoing advancements.