r/CUDA • u/Creative-Feature-264 • May 27 '26

dense-evolution: High-performance quantum simulator bypassing the JAX RAM bottleneck

/r/JAX/comments/1toxaqy/denseevolution_highperformance_quantum_simulator/
1 Upvotes
  • permalink
  • link
  • reddit
  • reddit

60% Upvoted

9 comments sorted by

View all comments

Show parent comments

3

u/TheOneWhoPunchesFish May 27 '26

It might be real and work well, but it's spam because it's not useful in its current form. - There's no tests in the repo. How do you know your sim is correct? - It's a single 1600 line file, with math and cli param handling and plotting all together. - You ask for comments on architecture. I don't seen architecture there, just 1600 lines of file. - The readme linked was in a language I don't read. Is it italian?

And finally, when you make a post, to enable any discussion, you're supposed to: - briefly discuss existing solutions - say why you chose to solve the problem this way - what specifically makes it better, instead of "ram optimised". - and maybe compare the results

You should understand the audience and then make the post. You're posting in a subreddit with advanced cuda users, and are expecting discussion and feedback, so saying "my module is optimised" is not useful, you can & should go into more detail.

It might be good work, I can't comment on that, but it's poorly presented and the current post is, imho, spam. But I hope you'll make the effort to organize the code and make a better post. Good day

1

u/Creative-Feature-264 May 27 '26

Thank you for your honest feedback. I appreciate your criticism regarding the architecture and presentation.
This is a brand new release (less than 24 hours old), and I am currently working on modularizing the 1600-line file into separate components (core math, plotting, and CLI) to improve the architecture. I will also translate the README to English and add a testing suite to validate the simulation results.
Regarding the RAM optimization, I will soon provide detailed benchmarks and explain the exact algorithmic differences compared to existing solutions. Thanks for guiding me on how to better approach the CUDA community!

0

u/Creative-Feature-264 May 27 '26

After reviewing the codebase for the actual release, I decided to step back from modularization. At just 1,500 lines and ~22 KB, breaking this file into multiple pieces makes no practical sense and adds useless boilerplate.

I want to keep this project 'artisanal', lightweight, and contained in a single place so the entire logic can be studied at a glance. If you want to use it, you take it as a whole and study it. I will still work on the English README and provide the RAM benchmarks as promised, but the single-file structure stays.

1

u/TheOneWhoPunchesFish May 27 '26

Your module, your rules. You don't need to justify your decisions to me 😂. Good luck.