User Controls

Lanny post your server specs and setup

  1. #1
    Dfg Tuskegee Airman [compulsively riposte the emigrant]
    Kinda curious.
  2. #2
    Bump
  3. #3
    Lanny Bird of Courage
    It's a pretty standard two server setup with one running the DB and one running the web server. Both are virtualized with the same "hardware" on each, exclusive control of 2 cores out of an E5, 2GB RAM, 60GB of SSD storage. The DB is postgres and that's pretty much the only thing that runs on that server. The other one runs nginx in front of uwsgi. The deploy process is a little janky because the builds happen on the web server but it works out fine.

    Anything in particular you wanted to know?
    The following users say it would be alright if the author of this post didn't die in a fire!
  4. #4
    GasTheKikesRaceWarNow Houston [this unquestioningly unfrequented clast]
    Isn't that massive overkill? Why do you need such high specs? Why not just run both the DB and the website on the same machine?

    And why not go "cloud"?
  5. #5
    Originally posted by GasTheKikesRaceWarNow Isn't that massive overkill? Why do you need such high specs? Why not just run both the DB and the website on the same machine?

    And why not go "cloud"?

    Which part of that setup is overkill lol? Just the fact there’s 2 machines? I would guess for redundancy
  6. #6
    Lanny Bird of Courage
    Originally posted by GasTheKikesRaceWarNow Isn't that massive overkill? Why do you need such high specs? Why not just run both the DB and the website on the same machine?

    And why not go "cloud"?

    I mean it is definitely enough to handle a lot more load than it gets but the servers are pretty cheap. DB and web server on the same machine generally isn't what you want, it's one of the few places where you can scale and get super-linear improvements. The real motivation is the build process mentioned earlier can slurp down a lot of memory, and the DB will generally expand caches to fill main memory, so we would get degraded performance and occasionally failed deployments if the OOM killer decided to knockout the build process. The real answer is of course to build locally but the time it would take to write that probably equates to a year worth of hosting costs so I couldn't be fucked with it.
  7. #7
    but are there sweet NIS logos on the tower case and stuff
  8. #8
    SBTlauien African Astronaut
    Originally posted by greenplastic but are there sweet NIS logos on the tower case and stuff

    Yes, in the NIS corporate office suite.
    The following users say it would be alright if the author of this post didn't die in a fire!
  9. #9
    Once /pol/ is finally shut down by the ZOG we can expect a flood of users here, so overkill is good
  10. #10
    Originally posted by inb4l0pht Once /pol/ is finally shut down by the ZOG we can expect a flood of users here, so overkill is good

    Nobody gives a shit about this niche-ass website
  11. #11
    Dfg Tuskegee Airman [compulsively riposte the emigrant]
    Originally posted by Lanny It's a pretty standard two server setup with one running the DB and one running the web server. Both are virtualized with the same "hardware" on each, exclusive control of 2 cores out of an E5, 2GB RAM, 60GB of SSD storage. The DB is postgres and that's pretty much the only thing that runs on that server. The other one runs nginx in front of uwsgi. The deploy process is a little janky because the builds happen on the web server but it works out fine.

    Anything in particular you wanted to know?

    Fascinating, I got two dedicated servers, one is on cloudlinux, the other on centos, which will port to cloudlinux. Generally keep the database on the same server, might switch it out if the load increases. I get a lot of traffic but the server is quite capable (24 cores, 128GB RAM etc).
  12. #12
    xy0 Houston
    Somewhat off topic, but i have a few VPSs (legacy from when i worked at a major hosting company) and 90GB of ram on a home lab setup with gigabit to everything. How can I make money? The damn power consumption of my home lab is about 250$ a month.. not to mention cooling in the summer.

    I'd love to have a purpose other than my own silly projects
  13. #13
    Dfg Tuskegee Airman [compulsively riposte the emigrant]
    Originally posted by xy0 Somewhat off topic, but i have a few VPSs (legacy from when i worked at a major hosting company) and 90GB of ram on a home lab setup with gigabit to everything. How can I make money? The damn power consumption of my home lab is about 250$ a month.. not to mention cooling in the summer.

    I'd love to have a purpose other than my own silly projects

    Honestly out of ideas on that one, I have few but I don't see enough ROI considering you're keeping things at your place. Unless you have a beefy rendering system and are into 3D, you could potentially fiverr your way out of it.

    What skillset do you have?
  14. #14
    GasTheKikesRaceWarNow Houston [this unquestioningly unfrequented clast]
    Originally posted by xy0 How can I make money?

    How secure is your connection? You could go niche - do bulletproof hosting, or seedbox hosting, or privacy compliant hosting for local businesses, or install solar and do eco-hosting. You won't be able to compete as a commodity.
  15. #15
    GasTheKikesRaceWarNow Houston [this unquestioningly unfrequented clast]
    Hay Lanny how do you deploy?

    Are you big on tests? CI?
  16. #16
    Lanny Bird of Courage
    Originally posted by GasTheKikesRaceWarNow Hay Lanny how do you deploy?

    Are you big on tests? CI?

    It's a pretty straight forward SSH script. The server schleps the latest code into a local repo, runs the build process, and drops the built files into a deployment location and bounces the app server. As mentioned it's not super elegant, it's probably the biggest piece of bad design in the codebase at the moment, the frontend code goes through its own build process but has to rely on some values that come from the forum's settings file (namely which forum extensions are installed), meaning the build process has to happen in the context of an actual installation so code has to be built in the context of the place it's going to be deployed. Fixing that is definitely on the todo list.

    I do have tests but they're not comprehensive, I try to write a test or two for each new feature but I'm not trying to get to some coverage number or anything, I just got tired of having to exercise 10 to 20 different workflows every time I changed something so the idea is more "automated smoke test" than "verify every behavior". Also there's nothing I hate more than a huge test suite that takes an hour to run and fails intermittently so the idea is more sanity checking than some promise of correctness.

    I do have a "CI" setup though Travis: https://travis-ci.org/RyanJenkins/ISS but people take CI to mean different things. Travis just tests code as it gets pushed to the repo, it doesn't auto deploy or anything.
    The following users say it would be alright if the author of this post didn't die in a fire!
  17. #17
    benny vader YELLOW GHOST
    Originally posted by xy0 Somewhat off topic, but i have a few VPSs (legacy from when i worked at a major hosting company) and 90GB of ram on a home lab setup with gigabit to everything. How can I make money? The damn power consumption of my home lab is about 250$ a month.. not to mention cooling in the summer.

    I'd love to have a purpose other than my own silly projects

    illicit pornography.
Jump to Top