krish678

12 ms·

1. 1.▲
   Private, advance operational testing under select regional franchise environment(app.qwoted.com)

   3 points by krish678 4mo ago|0 comments
2. 2.▲
   Show HN: System that keeps apps running when a server or region goes down

   3 points by krish678 5mo ago|0 comments
3. 3.▲
   by krish678 8mo ago

   I’m open-sourcing OpenTX, a production-grade payment gateway and canonical transaction protocol designed to modernize legacy ISO 8583 payment systems for cloud-native architectures. GitHub: https://github.com/krish567366&#x2
4. 4.▲
   Show HN: Why is ML inference still so ad-hoc in practice?

   4 points by krish678 9mo ago|0 comments
5. 5.▲
   by krish678 9mo ago

   That number is for a non-trivial software path (parsing, state updates, decision logic), not a minimal hot loop. Sub-100 ns in pure software usually means extremely constrained logic or offloading parts elsewhere. I agree there’s room to im
6. 6.▲
   by krish678 9mo ago

   Good point — ‘sub-microsecond’ is definitely more precise! Appreciate the feedback.
7. 7.▲
   by krish678 9mo ago

   I understand — the reviewers clearly see it differently, which is why they’ve been carefully evaluating my paper for the past 15 days.
8. 8.▲
   by krish678 9mo ago

   Not a bot — just a human who thinks em dashes pair nicely with tinsel. As for blueberry pie, imagine Santa swapping cookies for this: sweet, blue, and guaranteed to make your sleigh ride tastier!
9. 9.▲
   by krish678 9mo ago

   Thanks for pointing this out. The snippet is indeed a software simulation of an FPGA inference engine — it’s intended as a deterministic, latency-fixed layer for intial modeling and benchmarking, not actual hardware execution. The naming co
10. 10.▲
    by krish678 9mo ago

    Thankyou so much all this feedback. I’d also love to connect and discuss some of these points further if you’re open.
11. 11.▲
    by krish678 9mo ago

    Not a parody, just me trying to keep the thread constructive while sharing the project. Enjoying the discussion, even when it gets a bit wild.
12. 12.▲
    by krish678 9mo ago

    I hear you. I realize the repository and docs are dense and can be overwhelming. I’m actively working on cleaning up the presentation, improving examples, and making the intent and learning points easier to see. Thanks for your feedback.
13. 13.▲
    by krish678 9mo ago

    Congrats on the vacation vibes! Hope you enjoy some well-earned time offshore or wherever it takes you.
14. 14.▲
    by krish678 9mo ago

    The main goal is experimenting and sharing what I’ve learned. Seems like people are enjoying it, which is nice to see.
15. 15.▲
    by krish678 9mo ago

    Thanks for the perspective! The goal isn’t to get hired immediately for a super-specific role—it’s more about learning and experimenting with ultra-low-latency systems. I’m using it to understand CPU/NIC behavior, memory layouts, and r
16. 16.▲
    by krish678 9mo ago

    Thanks for asking! So far, optimizations are on x86—CPU pinning, NUMA layouts, huge pages, and custom NIC paths. Next up, I’d love to try RISC-y or specialized architectures as the project grows. The focus is still on learning and pushing l
17. 17.▲
    by krish678 9mo ago

    Thanks for checking out the repo. Broken links and top-level social URLs were my mistake—I’ll fix them. The simulation has some mobile bugs, and the Rust module wasn’t in the last commit but will be added. LLMs were used only for test scaff
18. 18.▲
    by krish678 9mo ago

    Not vibe coded! See the research (under peer review): https://www.preprints.org/manuscript/202512.2293 https://www.preprints.org/manuscript/202512.2270 All core code decisions were made after thor
19. 19.▲
    by krish678 9mo ago

    Thank you for taking the time to look through the repository. To all those who are calling it to be generated by AI. Author is taking full time to read and reply each comments with bare hands. To be fully transparent, LLM-assisted workflows
20. 20.▲
    by krish678 9mo ago

    Thank you for taking the time to look through the repository. To be transparent: LLM-assisted workflows were used in a limited capacity for unit test scaffolding and parts of the documentation, not for core system design or performance-crit
21. 21.▲
    by krish678 9mo ago

    Thanks for the observation! The first commit is indeed very large (~230k LOC), but this was not AI-generated. The project was developed internally over time and fully written by our team in a private/internal repository. Once the initi
22. 22.▲
    by krish678 9mo ago

    Thank you for taking the time to look through the repository. To be transparent: LLM-assisted workflows were used in a limited capacity for unit test scaffolding and parts of the documentation, not for core system design or performance-crit
23. 23.▲
    by krish678 9mo ago

    Thank you for taking the time to look through the repository. I’m continuing to iterate on both the code and the documentation to make the intent and technical details clearer. You can find my research paper(under peer review) here: https:
24. 24.▲
    by krish678 9mo ago

    That’s fair feedback — you’re right that the front-page wording overreaches given the current scope. The intent was to describe the performance and architectural targets (latency discipline, determinism, memory behavior) rather than to impl
25. 25.▲
    by krish678 9mo ago

    That’s a fair point, and I agree on wire-to-wire (SOF-in → SOF-out) hardware timestamps being the correct benchmark for HFT. The current numbers are software-level TSC samples (full frame available → TX start) and were intended to isolate t
26. 26.▲
    by krish678 9mo ago

    Fair point — agreed. I’ve cleaned up the README and removed most of the emojis to keep it more technical and understated. Thanks for the feedback.
27. 27.▲
    by krish678 9mo ago

    That’s a fair question — thanks for calling it out. The Rust component is a small, standalone module (used for the latency-critical fast path) that was referenced in the write-up but was not included in the last public commit due to an over
28. 28.▲
    by krish678 9mo ago

    Thank you for bringing this to my attention, and my sincere apologies for the oversight. The Rust file was inadvertently missed in the previous commit. I will update it promptly and ensure it is included correctly. Please give a star to rep
29. 29.▲
    Ultra-Low-Latency Trading System(submicro.krishnabajpai.me)

    30 points by krish678 9mo ago|64 comments
30. 30.▲
    by krish678 9mo ago

    Hi HN, I’m sharing a research-focused ultra-low-latency trading system I’ve been working on to explore how far software and systems-level optimizations can push decision latency on commodity hardware. What this is A research and learning fr