Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. GitHub Pages
  3. Performance

Performance

Scheduled Pinned Locked Moved Solved GitHub Pages
6 Posts 3 Posters 1.2k Views 3 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • G Offline
      G Offline
      gerben
      wrote on last edited by
      #1

      Hi, this drop-in replacement for Github Pages works great.

      Looking at the source code, it looks like the pages are served directly by the Express framework in NodeJS; correct? I wonder how well this performs under load; any estimates/experiences? (we are considering hosting redecentralize.org on our own server, but are a little worried about e.g. a slashdot effect taking it down when it is needed most..)

      The Express docs suggest running e.g. nginx as a cache in front of it, might that be a good idea? And if not, perhaps at least the app could use gzip compression?

      (besides, using an nginx server might also be useful to e.g. obtain server logs for statistics, but that’s a separate question)

      girishG 2 Replies Last reply
      2
      • robiR Offline
        robiR Offline
        robi
        wrote on last edited by
        #2

        I'd suggest having a cut-ver site on netlify in case of high traffic

        Conscious tech

        1 Reply Last reply
        0
        • G gerben

          Hi, this drop-in replacement for Github Pages works great.

          Looking at the source code, it looks like the pages are served directly by the Express framework in NodeJS; correct? I wonder how well this performs under load; any estimates/experiences? (we are considering hosting redecentralize.org on our own server, but are a little worried about e.g. a slashdot effect taking it down when it is needed most..)

          The Express docs suggest running e.g. nginx as a cache in front of it, might that be a good idea? And if not, perhaps at least the app could use gzip compression?

          (besides, using an nginx server might also be useful to e.g. obtain server logs for statistics, but that’s a separate question)

          girishG Offline
          girishG Offline
          girish
          Staff
          wrote on last edited by
          #3

          @gerben That's correct, the app is just served up using express.static. I don't have any performance numbers but it should work fine for normal loads like say even 100 hits a second. For higher loads, I recommend fronting the site with something like cloudflare.

          Currently, there is already a nginx in the front (the reverse proxy) but the app does not have caching. Note that both caching and gzip won't really add that much speed since most sites are mostly static pages are small enough to not be useful for zip and unzip operations (just cpu load). The reverse proxy does have http2 so we should see the benefits of parallel/concurrent http requests.

          For nginx logs, services -> nginx should have the logs 🙂

          On a side note, currently the app uses git+http auth, I plan to move it to ssh key based auth soonish. Any other suggestions welcome!

          1 Reply Last reply
          2
          • G gerben

            Hi, this drop-in replacement for Github Pages works great.

            Looking at the source code, it looks like the pages are served directly by the Express framework in NodeJS; correct? I wonder how well this performs under load; any estimates/experiences? (we are considering hosting redecentralize.org on our own server, but are a little worried about e.g. a slashdot effect taking it down when it is needed most..)

            The Express docs suggest running e.g. nginx as a cache in front of it, might that be a good idea? And if not, perhaps at least the app could use gzip compression?

            (besides, using an nginx server might also be useful to e.g. obtain server logs for statistics, but that’s a separate question)

            girishG Offline
            girishG Offline
            girish
            Staff
            wrote on last edited by
            #4

            @gerben BTW, is the site already on GitHub pages app? It's plenty fast from here atleast (from the US/CA). I also found https://redecentralize.org/interviews/ (fantastic!), this is going to keep me occupied for a while 🙂

            G 1 Reply Last reply
            1
            • girishG girish

              @gerben BTW, is the site already on GitHub pages app? It's plenty fast from here atleast (from the US/CA). I also found https://redecentralize.org/interviews/ (fantastic!), this is going to keep me occupied for a while 🙂

              G Offline
              G Offline
              gerben
              wrote on last edited by
              #5

              @girish Thanks for the response!

              For higher loads, I recommend fronting the site with something like cloudflare.

              We might indeed try use such a CDN if it turns out to be needed (probably not cloudflare, to not centralise the web too much). Ideally people would all just get our site via peer-to-peer delivery instead. 😉

              @girish said in Performance:

              @gerben BTW, is the site already on GitHub pages app?

              No, currently our server runs a copy at web.redecentralize.org; from this speed test it looks like you’d have 1.66 second when visiting from San Francisco (to Amsterdam). Not as good as the 550ms I get for redecentralize.org (i.e. GitHub’s servers/CDN), but acceptable I guess. I see we could also trim some file sizes..

              I also found https://redecentralize.org/interviews/ (fantastic!), this is going to keep me occupied for a while 🙂

              Enjoy. 🙂

              girishG 1 Reply Last reply
              0
              • G gerben

                @girish Thanks for the response!

                For higher loads, I recommend fronting the site with something like cloudflare.

                We might indeed try use such a CDN if it turns out to be needed (probably not cloudflare, to not centralise the web too much). Ideally people would all just get our site via peer-to-peer delivery instead. 😉

                @girish said in Performance:

                @gerben BTW, is the site already on GitHub pages app?

                No, currently our server runs a copy at web.redecentralize.org; from this speed test it looks like you’d have 1.66 second when visiting from San Francisco (to Amsterdam). Not as good as the 550ms I get for redecentralize.org (i.e. GitHub’s servers/CDN), but acceptable I guess. I see we could also trim some file sizes..

                I also found https://redecentralize.org/interviews/ (fantastic!), this is going to keep me occupied for a while 🙂

                Enjoy. 🙂

                girishG Offline
                girishG Offline
                girish
                Staff
                wrote on last edited by
                #6

                @gerben said in Performance:

                We might indeed try use such a CDN if it turns out to be needed (probably not cloudflare, to not centralise the web too much). Ideally people would all just get our site via peer-to-peer delivery instead.

                Totally agreed. We self-host pretty much everything (other than the servers itself). Though I suggested Cloudflare, I was really nudging you towards maybe using a CDN since CDN has it's use cases. People have suggested BunnyCDN as well. That said, we don't use CDN ourselves, even for https://cloudron.io and https://docs.cloudron.io. It's served from surfer. This is mostly for ideological reasons, we are willing to give up on some speed and not centralize (we used to have it on AWS Cloudfront before).

                1 Reply Last reply
                3
                Reply
                • Reply as topic
                Log in to reply
                • Oldest to Newest
                • Newest to Oldest
                • Most Votes


                  • Login

                  • Don't have an account? Register

                  • Login or register to search.
                  • First post
                    Last post
                  0
                  • Categories
                  • Recent
                  • Tags
                  • Popular
                  • Bookmarks
                  • Search