We are currently working on new rules for what content should and shouldn't be allowed on this website, and are looking for feedback! See Esolang:2026 topicality proposal to view and give feedback on the current draft.
Talk:Brainfuck speed test
Please try mine too
I've got one for you: https://codeberg.org/splot-dev/splotbf#installation, thank you. It should work on Windows... although tell me if it doesn't. —User:Splot-dev
- OK, I'll use the source code next time I retest (soon). --None1 (Nope.) 06:45, 13 August 2026 (UTC)
- I'm sorry but your interpreter cannot interpret dbfi when not debugging (it runs into an infinite loop), so I'm not adding it this time. --None1 (Nope.) 15:04, 14 August 2026 (UTC)
- Oh! what was happening was that you didn't wait for dbfi to start accepting input—hence the infinite loop! Here, I made the benchmark for you.
- Try this please (read the bolded notes): https://esolangs.org/wiki/User:Splot-dev/splotbf/benchmark
- Also, please update splotbf to v1.3.1:
pip install splotbf --upgrade
- —User:Splot-dev
- OK. I still wonder why your interpreter needs a long time to load. --None1 (Nope.) 06:53, 17 August 2026 (UTC)
- Your benchmark program raises AttributeError: module 'pexpect' has no attribute 'spawn'. I had both packages upgraded before running. --None1 (Nope.) 08:18, 17 August 2026 (UTC)
- I fixed it, but your program ran for more than 5min, so I can't add it. --None1 (Nope.) 09:08, 17 August 2026 (UTC)
- This is very confusing: I'm getting 'Time: 4.08881729200948 seconds.'. I believe that pexpect is not supported for Windows, and the I/O format of PopenSpawn, which you might've used to fix it, is not supported by splotbf.
- Well, I'm not gonna try at this anymore.
- —User:Splot-dev
Hello, could you please try my bf interpreter and bf-to-rust transpiler?
https://github.com/pro465/bf-rs
Thanks! --Pro465 (talk) 15:18, 5 September 2023 (UTC)
Ok, I'll try it later. --None1 (talk) 13:36, 6 September 2023 (UTC)
I've tested your interpreter and it takes about 3 secs to run. I modified your interpreter so that works under Windows. Unfortunately, I can't test your compiler because I can't modify it so that it works under Windows probably because I'm not good enough at Rust, please modify it yourself so that I can run it correctly on my computer. --None1 (talk) 14:44, 6 September 2023 (UTC)
- thanks and sorry! I fixed it now and tested it under W11, so could you please try again?
(I'll fix the interpreter too -- it probably could also be a lot faster now that I'm more experienced in rust).
btw you are running cargo b --release, right?
--Pro465 (talk) 17:31, 6 September 2023 (UTC)
I've tested compiler, it took about 0.8 seconds. (Note: Unlike what you expected, I run rustc main.rs) --None1 (talk) 09:26, 7 September 2023 (UTC)
- thanks!
> Unlike what you expected, I run rustc main.rs
- I don't think that's fair unless you are using debug builds on other langs too. If you wanna use rustc in release mode, try
rustc -C opt-level=3 main.rs, it would be a lot faster. --Pro465 (talk) 12:09, 7 September 2023 (UTC)
I retested, now that the interpreter takes 0.2 secs to run and the compiler takes 0.6 secs. --None1 (talk) 12:52, 7 September 2023 (UTC)
- what about the other projects? all of them probably could be faster by enabling optimizations (unfortunately I am not experienced enough in them to tell you how to add optimizations) --Pro465 (talk) 13:32, 7 September 2023 (UTC)
- Other projects are all either already optimized or doesn't support optimizing, I'm not sure about brainfuck-rs though, I downloaded it through its Windows distribution. --None1 (talk) 13:56, 7 September 2023 (UTC)
- OK, thanks and have a great day/night --Pro465 (talk) 14:29, 7 September 2023 (UTC)
oh, mine is terrible at this. even when you set step time to 0. tommyaweosme 13:04, 28 July 2024 (UTC)
Hey this is Sree - I provided the full source for mine, though haven't tried under Windows for years (It should still work though)
https://github.com/sreekotay/bffsree
Logarithmic or inverse scale for the bar chart?
That bar chart looks very unclear, because the fast ones are just very short, becoming a horizontal line. Maybe use the inverse of the time(to get the speed) or logarithmic scale. Also have you tested this? -- i s l p t n g 01:20, 17 August 2026 (UTC)
- UR right. I'll add your interpreter next time. I'm also trying to add Urban Muller's interpreter if I can change the number of cells. --None1 (Nope.) 05:52, 17 August 2026 (UTC)
- I've added inverse and logarithmic charts and tested your interpreter. Your interpreter ran really fast and took only 107ms to run in average. --None1 (Nope.) 11:48, 17 August 2026 (UTC)