a thoughtful web.
Good ideas and conversation. No ads, no tracking.   Login or Take a Tour!
comment
rob05c  ·  3058 days ago  ·  link  ·    ·  parent  ·  post: Devski Update: Notifications in SQL, Post Performance Fix

We currently pay for a VM with 16G of RAM. The app is currently using 2.5G. In the past it's used over 8G, so we feel the need for at least 16. We are running Hubski with everything in RAM at the moment. I've made a few small tables load dynamically, but +95% of our data, all publications (posts and comments) are still loaded into RAM on startup.

Again, that's one of the things I'm working on fixing, and one of the primary motivations of moving to SQL. Moving to SQL doesn't get things out of RAM automatically. We still have to do additional refactoring to make things load as-needed from the HDD.

I said 'HDD', but our host uses entirely SSDs, so we get that for free.

    Do you see any of the possible programmatical constructions you've mentioned being used as a base for Hubski some time later?

Probably not. One of these days I'll probably spend a weekend configuring Wordpress to look like Hubski, and see what it looks like. But, we want an API anyway: the most likely scenario is, once all data is in SQL, creating an API that serves all data needed by every page on hubski.com, and then "rewriting" hubski.com as a static html page that queries the API, and the "main app" goes away.