24
alturnativ
363d

There's a lil tool someone wrote that runs as a post build event for one of our projects. I got bored of watching that tool hog a single CPU thread for like half a minute each time I had to build, so I tried making the thing multi-threaded...

...and it worked! Shit runs on all threads for just a few seconds now 💪🏻

Comments
  • 12
    I also read the docs on some of the libs used in that tool and brought memory usage down from around 14GB (when first getting it to run in parallel) to a couple hundred MB. Double win!
  • 12
    Imposter syndrome can suck it (until tomorrow at least)
  • 2
    What the fuck was is doing? Using 14G in a (post) build step is quite the achievement.
  • 2
    @hjk101 it was doing this a couple hundred times for about 10 or so references, ha

    https://learn.microsoft.com/en-us/...

    It was also doing it repeatedly for those same references for each process, so I added thread-safe caching to cut down on that repetition also.
  • 1
    @alturnativ print the diff to a big poster, put into a simple black frame, and in bold text "I made this. Imposter syndrome can suck it."
  • 1
    @Wisecrack as long as I don't have to do the same for all the times I accidentally slowed things down 😅
  • 0
    @alturnativ never forget "best foot forward."
Add Comment