pull down to refresh

I haven't seen a case study swooning or anything about LND with postgres. I'm curious if it's better for a production use case with 10000x the "load" of a normal routing node or if it's merely more convenient than the embedded db devops wise.
11.2k sats \ 0 replies \ @aljaz 26 Sep
i'm assuming you're talking about the real postgres integration that LL is working on, not the KV joke. There is performance testing from alby from a year and a half ago for the KV one
i missed the latest LLabs roundtable but there are generally several problems to performance:
  • external database adds network latency and round trips over boltdb
  • you need very good architecture, schema and implementation due to row/table locking with updates etc
  • if you have synchronous replication for high availability you inject more latency into the process
Generally I don't think you'd want to be the early adopter of this if you want a high performance node since i'd expect a mixed bag of results and issues before the database gets polished enough. I'm also not sure postgresql integration, if done with 1:1 mapping is ever gonna be as high performance as boltdb. But I have not kept up2date with latest developments and architecture changes in lnd to see how they envisioned this migration and getting the performance up for it.
reply
Didn’t know that existed.
Probably better all around, especially since you’re already running Postgres.
I’m thinking data analysis.
I don’t even know what the embedded db is for the LND, written in Golang.
I also don’t know how they shoved LND golang app into a phone with Zeus.
I also don’t know how to convince anybody to work on a project with me.
reply
I don't know why you comment if you don't know nothing.
reply
Giving ideas on what all questions need answered in the wild Wild West.
reply
I will be coming in v0.19. Ziggie is working on it.
reply
I think that is a @DarthCoin question.
reply
no, we already have the mighty LN chad here that answered to that specific technical question.
reply
You were a little late today.
reply