Kansas Crimson

The server peeps have done nothing to help -- I'm going to test some stuff over the next couple days.
At best, we grab our database and port it over to a new build and that works.
At worst, we start from scratch, with a fresh bored ( that will look the same but not include all previous posts -- I would lock that bored from future posts but keep it alive for reference ).

Hold on to your butts.

Cheeks firmly grasped.

It's worked great on my phone all day.

Is there any way Japhy can help -- financially, I mean?

defixione wrote: ↑Wed Sep 27, 2023 7:03 pm It's worked great on my phone all day.

That's just happenstance ( and the super strange thing with the issues ).
Some work came up yesterday which will spill to today.
I'm aiming for Friday though.

OK, I haven't done anything but the boreds over the last 24 hours seem normal.
( though I did threaten to leave our host provider 3 days ago -- maybe things got adjusted )

I'm going to not do the things I said above just to see how the next few days go.
Let me know here if you all are experiencing those goddamn slow responses and 503's again.

pdub wrote: ↑Fri Sep 29, 2023 9:20 am OK, I haven't done anything but the boreds over the last 24 hours seem normal.
( though I did threaten to leave our host provider 3 days ago -- maybe things got adjusted )

I'm going to not do the things I said above just to see how the next few days go.
Let me know here if you all are experiencing those goddamn slow responses and 503's again.

I haven't had any problems in the last day or two, either.

Fingers crossed again but I think they upped our max usage.

I’m seeing only fast loads.

Again, not a server guy, but I’m finding it difficult for it just to be coincidental.

No one can prove to me he didn't.

Server resources, story of the week.

I made a decision six months ago to have a team rip out it's code and replace it with a completely new implementation using a tool that it seemed like we were just slowly writing on our own unknowingly (dbt, for those curious). We're just using it in a way that it's not meant to be used - live reporting, instead of batch processing. Cool, we're being innovative.

Yesterday found that it's running slowly. Saw in the docs that it explicitly warns that when your project gets big the compilation time is slow. 30 second compilations on top of our query time is completely unacceptable, and it's just going to get worse as this thing grows. This means that the entire pivot is fucked, and we just wasted six months, and now we're not going to hit the deadline to get off the contract for the third party software we're trying to replace, which is going to cost us five million dollars. I went home, told my wife that if I were my company I'd fire me, and was an absolute wreck for about 24 hours.

Today I discovered that it's taking 30+ seconds because our infrastructure team allots, by default, 1/4th of a CPU core to each Kubernetes pod. It runs in five seconds on my Mac, yet in our fucking production environment we have a tiny fraction of the hardware that our individual computers have. I just have to go through some corporate hoops to justify the cost of running our production applications on hardware that's as good as our individual fucking laptops.

I don't expect anyone to read this; purely cathartic.

tl;dr - Fuck the cloud.

I didnt read any of that. One, because I wouldn't understand it anyway and; Two, because it just sounds like and an old man yelling at...the clouds....

TDub wrote: ↑Sat Sep 30, 2023 8:39 am I didnt read any of that. One, because I wouldn't understand it anyway and; Two, because it just sounds like and an old man yelling at...the clouds....

That all made sense to me and I enjoyed the read. Thank you.

So like, clearly this was a server problem, right?

And they gave us the resources we deserved after I said I’d leave?

pdub wrote: ↑Sat Sep 30, 2023 3:48 pm So like, clearly this was a server problem, right?

And they gave us the resources we deserved after I said I’d leave?

everybody knew that

I musta been the only one who didn’t.

literally

Shirley wrote: ↑Sat Sep 30, 2023 2:23 pm

TDub wrote: ↑Sat Sep 30, 2023 8:39 am I didnt read any of that. One, because I wouldn't understand it anyway and; Two, because it just sounds like and an old man yelling at...the clouds....

Abe Simpson . . . Isn’t he the one who turned cats and dogs against each other?

pdub wrote: ↑Fri Sep 29, 2023 7:21 pm Fingers crossed again but I think they upped our max usage.

I’m seeing only fast loads.

Again, not a server guy, but I’m finding it difficult for it just to be coincidental.

They will never admit they were skimping you. Welcome to IT. "I have no idea what you're talking about" followed by fixing the problem ASAP (AKA the Visa Special).

I caught Visa doing one of these that was costing more than $100k per year. I put together an exhaustively researched case that clearly showed they were doing it. We finally got all their key players into a meeting and presented our case. They claimed that every other piece between them and us was responsible and that all of my research was inaccurate.

The next week their code magically stopped doing what it had been doing.

To be fair, I will sometimes, on a more minor level, do this too if a client catches something I missed.
"Must be a cache problem,"
- web devs everywhere