Everytime Lobste.rs get posted, I get to think should I dive in. This time maybe. Could somebody be kind enough to give me an invite. Email in my profile. Thanks.
Lobste.rs is now running on SQLite
161–170 of 209 posts
Re: Lobste.rs is now running on SQLite
#162Earlier quoted context omitted.
As a big user of MySQL - moving off of it does seem like a good idea, if you can. The longer you wait, the harder it will be to flee
Any reason besides trust me bro?
- Its query planner is ancient and broken - it comes up with very bad plans. Every time we rely on it, we regret it eventually
- you have to use locks to prevent mangled write transactions, instead of the db handling it. Jepsen report is scathing
- its pretty hard to set it up in semi-sync replication mode, a.k.a. "only return from a transaction commit when the transaction is present on at least one other replica". Once you've set it up, you have to deal with insane things like transactions being visible on replicas before leaders, or even worse transactions visible on replicas briefly but never visible on leaders or other replicas
- every knob and feature contains subtle bugs, sometimes ones as scary as index corruption, that you only discover after it has caused you pain
I don't know why you would choose it unless you were already running it
Re: Lobste.rs is now running on SQLite
#163Re: Lobste.rs is now running on SQLite
#164It's been fairly unstable recently, pages sometimes render for several seconds which I've never seen under MariaDB. Used to be instantaneous, always. Sometimes (maybe 5% or less) the request won't render at all, and you get a browser error page. Today they ran into this bug, lost a bunch of voting data, and went into read-only mode for several hours: https://github.com/rails/rails/pull/57128 I wonder how much of this…
It's super slow.
Re: Lobste.rs is now running on SQLite
#165Earlier quoted context omitted.
Every time it happens there's a sub-thread asking about the weird timestamps and dang replies to it saying changing the timestamps is done so that there won't be a sub-thread about the weird timestamps.
I'm pretty sure this comment chain is in every popular 2nd chance pool post though anyway
True. I don't understand why they overwrite the date at all actually, for either the post or the comments, that sounds like the hackiest way of implementing the “second chance pool” feature.
Re: Lobste.rs is now running on SQLite
#166It's been fairly unstable recently, pages sometimes render for several seconds which I've never seen under MariaDB. Used to be instantaneous, always. Sometimes (maybe 5% or less) the request won't render at all, and you get a browser error page. Today they ran into this bug, lost a bunch of voting data, and went into read-only mode for several hours: https://github.com/rails/rails/pull/57128 I wonder how much of this…
SQLite definitely seems like a poor choice for dealing with many concurrent requests. Maybe it's improved since I last used it, but to my knowledge SQLite essentially forces all writes to be serialised, at risk of data corruption otherwise. There are tricks for improving the performance such as WALs, but that is merely a performance boost rather than genuine concurrency with things like row-level locks that you might…
Can't you do infinity read replicas? I don't think the write load on lobster.rs is severe - maybe 1 comment/sec, with an acceptable replication delay of 60 sec?
If you can do that, you can have infinity instances.
Re: Lobste.rs is now running on SQLite
#167I would visit lobste.rs more if it filtered out stories that are on Hacker News.
I'm not interested in a rehash of Hacker News but I am interested in more tech news.
Anyhow on topic: I find it puzzling the whole "use sqlite in production!" thing.
- you're stuck on a single machine now.
- you don't have remote database access.
- you have to live with the inflexibility of sqlite's schema change capability.
- all writes go through a single writer.
- fewer data types
- fewer backup/security/high availability options
- foreign keys and strict disabled by default.
- you're single core in a multi core world.
It's not a terrible decision but when you can choose Postgres, why would you go with sqlite?
Re: Lobste.rs is now running on SQLite
#168Software “engineering”. Thank goodness bridges aren’t built with this level of rigor. In any case I will take an invite if one has one because the community is solid.
I've got a few planks over a ditch in my garden. The bridge only needs to be designed for the load and then some. In this case, this seems to work just fine.
Re: Lobste.rs is now running on SQLite
#169I would visit lobste.rs more if it filtered out stories that are on Hacker News. I'm not interested in a rehash of Hacker News but I am interested in more tech news. Anyhow on topic: I find it puzzling the whole "use sqlite in production!" thing. - you're stuck on a single machine now. - you don't have remote database access. - you have to live with the inflexibility of sqlite's schema change capability. - all writes…
A single page answers that question: https://www.sqlite.org/whentouse.html
Re: Lobste.rs is now running on SQLite
#170Earlier quoted context omitted.
I think it is better to have some elitist communities, than to drag everyone down to some least common denomination... I think that was one of the big mistakes/oversight that came with the Internet..
I think some are fine, but if I had to choose one I'd choose open access, so I think it's the more important of the two. And in fact it's because the web is open, "no permission needed" by default that allows elitist groups to exist on the web. So I don't think I see it as a mistake. The alternative would be... You can only create a website if you're invited to the internet by someone who already has access? You have…
>Those were all potential futures we imo thankfully and carefully avoided!
I am not so thankful. But it is coming from my view of the current world.
I think open Internet for business is good. But open Internet for communication was bad. I cannot think of one good thing that have resulted from an open internet for communication/discussions. It has turned out to result in a collective, perpetual state of seizure for all humanity.
I am someone who had to learn stuff from random encounters with books in the 90s. Even then, I would not have it any other way...