4 ms·
next up: custom FizzBuzz ASIC with 128 fizz and 128 buzz cores for maximum throughput.
by no_time 5y ago
next up: custom FizzBuzz ASIC with 128 fizz and 128 buzz cores for maximum throughput.
- function_seven 5y agoSubstandard design. You should have a suitable ratio of cores to keep them load balanced. I suggest 160 fizz cores and 96 buzz cores. EDIT: And a fizzbuzz co-processor, obviously.
- gumby 5y ago> fizzbuzz co-processor, obviously One of the functional modules on the M1 Pro Max chip, but only the Max one, unfortunately. Take that, Intel!
- mordechai9000 5y agoI think optimizing binary tree inversion is a higher priority, right now.
- WJW 5y agoNot for fizzbuzz optimisation it isn't! Get your priorities straight mate! Who is trying to get hired when we could be outputting more fizzes and/or buzzes! :)
- randy408 5y agoFizzBuzzCoin?
- deleted 5y ago[deleted]
- wtallis 5y agoOr if your ASIC generalizes the problem in a slightly different direction, you end up reinventing TWINKLE and TWIRL: https://en.wikipedia.org/wiki/TWINKLE https://en.wikipedia.org/wiki/TWINKLE
- nomaxx117 5y agoThanks for sharing this, its always amazing to see how physical properties can be used in weird ways to bypass normal "rules" of computation.
- nonameiguess 5y agoCould probably store all multiples of 3 and 5 up to some really big number burned directly to hardware and then do something like a big CAM table the way Internet core routers do mapping the numbers to ASCII bit strings. Then speedup IO by not having a general purpose display, but something more like an old-school digital clock that can only show digits and the words "fizz" and "buzz."
- function_seven 5y agoYou'll get docked points from the typography nerd for displaying "fizz" instead of "fizz"
- yuliyp 5y agoThat's definitely not going to be useful. By doing this 15 numbers at a time you completely avoid needing to do any division anyway. print FB, i+1. i+2, Fizz, i+3, Buzz. i+4, ... i+14. Then increment by 15. Also, even with a very slow CPU you'd already run faster than can be perceived on a digital clock
- Ericson2314 5y agoThat would be easier.
- vsareto 5y agoAh yes, the new junior developer technical interview