Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
JosephjackJR
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
1.
▲
Engineer made built in memory, loop detection and audits mandatory for agents
(github.com)
2 points
by
JosephjackJR
3mo ago
|
1 comments
2.
▲
by
JosephjackJR
3mo ago
Has anyone else used this? I just started using it and it is pretty damn cool to say the least. If anyone has used it, how does it hold up with 50 agents in production, and is it possible to use circuit breakers for more than one agent simu
3.
▲
I beat mem0 on long eval memory and could not care less
(octopodas.com)
4 points
by
JosephjackJR
3mo ago
|
0 comments
4.
▲
by
JosephjackJR
7mo ago
hit this building agent systems - context gone on restart. Built a dedicated memory layer for agent workloads, in-process, survives restarts via WAL recovery. Happy to share: https://github.com/RYJOX-Technologies/Synrix
5.
▲
by
JosephjackJR
7mo ago
Concurrent agent memory is hard most solutions aren't designed for multiple agents writing at once. Built something in-process. Happy to share: https://github.com/RYJOX-Technologies/Synrix-Memory-Engine
6.
▲
by
JosephjackJR
7mo ago
Ran into the same thing. SQLite works until you need cold start recovery or WAL contention with concurrent agents. Built a dedicated memory layer for agent workloads - happy to share: https://github.com/RYJOX-Technologies&#x
7.
▲
Show HN: Local memory layer for AI agents, survives restarts, no embeddings
(screenapp.io)
2 points
by
JosephjackJR
7mo ago
|
0 comments
8.
▲
by
JosephjackJR
7mo ago
super easy; we are currently trialing it with people who have this issue, check out our website or github, we will happily let you try anything you want with it. Really want feedback ideally atm.
9.
▲
Agent memory is structured not fuzzy.why are we all using vector DBs for it?
(old.reddit.com)
2 points
by
JosephjackJR
7mo ago
|
3 comments
10.
▲
by
JosephjackJR
7mo ago
I built a local-first AI memory engine for agents and edge systems. It uses a Binary Lattice instead of vectors. Fixed-size nodes with arithmetic addressing, so lookups are O(1) by ID and O(k) by prefix where k is result count not corpus si
11.
▲
by
JosephjackJR
7mo ago
Over the past year I’ve been working on a local-first memory engine for AI systems. This started from debugging agent workflows that behaved differently after restarts. In several cases the memory layer relied on embeddings and approximate
12.
▲
by
JosephjackJR
8mo ago
If anyone is working on something similar please drop link below so i can check it out!
13.
▲
Two orders of magnitude faster Persistent AI memory via a binary lattice
(github.com)
1 points
by
JosephjackJR
8mo ago
|
2 comments
14.
▲
by
JosephjackJR
8mo ago
Retrieval performance is becoming a silent bottleneck for local first AI agents. While context windows are expanding, the latency involved in querying traditional cloud vector databases still sits in the 10ms to 50ms range due to network ho
15.
▲
Show HN: Synrix local-first memory engine (O(k) retrieval, no vectors, no cloud)
(github.com)
2 points
by
JosephjackJR
8mo ago
|
0 comments
16.
▲
by
JosephjackJR
9mo ago
It is a good point. However a lot of IT companies have differing Industries within it, not easy to paint with a simple brush of 'IT Company' like what would you define an IT company as?
17.
▲
Cloud costs are the #2 expense at midsize IT companies. Is this sustainable?
(cio.com)
1 points
by
JosephjackJR
9mo ago
|
3 comments
18.
▲
by
JosephjackJR
9mo ago
Just read a CIO article saying cloud costs are now the second biggest expense for midsize IT companies, behind labor and ahead of pretty much everything else. That matches what I keep hearing from people running real systems. Cloud spend do
19.
▲
by
JosephjackJR
9mo ago
I’ve been thinking about a problem that keeps resurfacing as AI systems become more autonomous and long running, but doesn’t seem to be discussed much outside of implementation details. Most AI systems today treat memory as ephemeral. Conte
20.
▲
by
JosephjackJR
9mo ago
Drones are one of our primary usecases; however it is actually applicable to memory loss in lets say LLM not necessarily with power loss, but with corruption, hallucination and persistent memory problems, from overload of data or data retri
21.
▲
The $1M Annual Cost of RAM-Bound Vector Databases in the Cloud
(synrix.substack.com)
2 points
by
JosephjackJR
10mo ago
|
2 comments
22.
▲
by
JosephjackJR
10mo ago
We analyzed the fundamental architectural flaw in today's cloud vector database paradigm: the hard dependency on RAM. This design forces platforms with massive data volumes (e.g., millions of video frames, billions of RAG documents) in
23.
▲
Show HN: Synrix – A Zero-Loss, Sub-Microsecond Memory Engine for Edge Compute
(ryjoxdemo.com)
3 points
by
JosephjackJR
10mo ago
|
0 comments
24.
▲
Fuck RAM Limits 50M Persistent Nodes on a $199 Jetson (186 ns, CPU-only)
(ryjoxdemo.com)
4 points
by
JosephjackJR
10mo ago
|
1 comments
25.
▲
by
JosephjackJR
10mo ago
Two-person team, eighteen months bootstrapped. We just shipped Synrix, a flat fixed-width memory-mapped lattice that runs fifty million persistent nodes on an eight gigabyte Jetson Orin Nano with 186 ns hot-path latency (under 3.2 cycles st
26.
▲
by
JosephjackJR
10mo ago
On consistency once the dataset spills off local storage: the entire lattice is fixed-size, block-aligned, and memory-mapped, so the kernel pages it exactly like RAM. We keep the hot path tolerant to minor faults (prefetch hints + careful a
27.
▲
by
JosephjackJR
10mo ago
This would be awesome. We are super early and thinking about potential use cases. This is simply one use case, but the system we have built has a lot more. Essentially we are going to start with its persistent memory aspect. What is the bes
28.
▲
by
JosephjackJR
10mo ago
Disappointing to see this. Only upside potentially more diversity of shows on netflix. Apart from that, no real benefit?
29.
▲
Why real-time AI memory is still slow, and a different approach
(drive.google.com)
2 points
by
JosephjackJR
10mo ago
|
5 comments
30.
▲
by
JosephjackJR
10mo ago
We’ve been experimenting with real-time AI memory systems and kept running into the same limitations: RAM-bound graphs, multi-millisecond access patterns, durability issues, and unpredictable behaviour under load. We tried approaching the p
More ›