| 1 person marked this as a favorite. |
It reveals that the experience must be excruciatingly slow for everyone.
Well, that's not true for me.
Remember that no one has a single piece of wire connecting their computer to the Paizo servers.
Everyone's route between home and Paizo goes through multiple routers, servers and cables. The slowness might be anywhere in that tangle of equipment.
Even if we live next door to each other, but one of us uses ATT servers/cables and the other uses Comcast, we're going to be routed to different equipment and use different access points for the internet.
| 2 people marked this as a favorite. |
You might want to change your posting alias. In English that could be taken as an offensive/sexist/personal insult.
...
I DO live in Europe so a part of that slowness probably stems from not having local servers.
I just tried a full reload of the paizo.com homepage [crtl]+[F5], and it took about 5 or 6 seconds to load. I'm in Austria, so Europe as well.
The blog takes a really long time to load all those images and videos from youtube and stuff. That is horrible. I mean, the subpage is responsive while it loads all the images, but it should not need to load all that in one go. It took about 2 minutes to finish loading.
paizo.com/store was taking about 5 seconds as well, so it seems to me, it's just the blog.
Software Architect
|
| 2 people marked this as a favorite. |
Thanks for the heads up, Franz. The blog page wasn't archiving posts properly, so it was sending far more content than it should have been. The page should now have a more reasonably sized payload which should load much more quickly.
Regarding speed more generally, a lot of the technology stack under which the site was originally built is *very* opinionated, which makes it difficult to substitute components. As such, most of our migration efforts so far have been "outside-in", focusing first on replacing the parts of our infrastructure that web requests hit first. Most of that migration process has been largely invisible, but it set us up for phase two - in which we use the upgraded infrastructure to seamlessly control which parts of the site are managed by a more flexible technology stack and which parts remain under control of the original technology.
Basically, as we continue migrating sections of the site, the performance and user experience should continue to improve. About 5% of the website's traffic is handled by the new stack, and we're regularly permitting it to handle more and more of the site. In parallel, we're also working on migrating larger components. These tend to be much more complicated and require more testing, but they also tend to be huge drivers of traffic - blog posts, the forums, the store, and so forth.
Finally, all of this is happening in the context of the tech team continuously patching existing bugs, upgrading and maintaining critical infrastructure, implementing legally mandated features in response to changing regulation, and supporting internal applications and services for Paizo's warehouse, customer service, finance, marketing, and creative teams, in addition to supporting Organized Play and our many business partners.
| 1 person marked this as a favorite. |
Thanks for the heads up, Franz. The blog page wasn't archiving posts properly, so it was sending far more content than it should have been. The page should now have a more reasonably sized payload which should load much more quickly.
...
It absolutely improved the blog loading. Pressing [ctrl]+[F5] on the blog now finishes loading in less than 20 seconds for me.
Good job Brian & Team!
| 1 person marked this as a favorite. |
Would like the echo the comments from Franz...blog loads “normally” now...really appreciate these improvements!