2:57 PM
@NexTerren r/PunPolice is funny.
Half of them hate puns, and the other half because they want to share great puns with the rest of the world.
There's a constant mild fight going on.
Between today and last Friday, I axed a second or few off the page load time of our site to get it fast enough to move to Azure (we're having trouble with the config, but we're almost fast enough for our metrics, so we decided to look at an obvious spot--our bad code).
And the irritating thing is, this should have been done years ago.
We could've had an average load of 1 second instead of 3, probably.
The longest load was 20ms with my change in one spot, compared to 850ms without it.
Median with it is 2, and median before was about 200.
The other call, I dropped from about 3 seconds to below 1 second.
This is with the debug flag set, so the boost won't be quite as visible in prod, but it'll be huge either way.
Our site will almost certainly end up faster on Azure than it ever was here, and we'll not stop tuning it.
(One other thing is, we're currently, unintentionally, running a pirated version of SQL Server Enterprise now, but are going to the cheaper version with this move. One of our hosting providers upgraded us and refused to bring us back down, even though we don't have a license for it. I don't know the details, but basically, we own the software on our systems, but we pay another company to manage it, which seems weird to me--especially since they break things more than they fix things.)
SQL Server Enterprise has several performance features that the other one doesn't, so that might be part of the performance hit we're seeing.