Help with Application Infrastructure / Architecture
-
So your IIS worker process is blocked, that IS a code issue. Likely the only fix for this is adding IIS workers and throwing threads at the issue. That's about it.
-
@jn19 said:
Session in AcquireRequestState
https://www.leansentry.com/Guide/IIS-AspNet-Hangs
They agree, this is something only the developers can fix. Hardware is not going to solve your problem. Your founder is sending you on a wild goose chase, I'm afraid.
-
@scottalanmiller said:
@jn19 said:
I've got full access to these machines but I have no software development experience, so I just want to do what I can to get things running more smoothly.
I'm not saying quit, but this is when you prep your resume and start looking. I'm not being funny in any way. It's impossible to read the situation from here, but everything that we are hearing is that you have completely incompetent developers and management and they are driving the product into the ground and throwing money away like crazy and are trying to blame IT for their failings.
I was thinking along these same lines.
-
@scottalanmiller said:
@Dashrender said:
From a platform perspective this seems strange to me that your devs are not the ones working to fix these issues.
Well, one of the problems with devs causing issues is that often they caused them because they don't really know what they are doing and so can't fix them because they aren't sure why or how it all works.
I agree that this is just a bad situation for the OP. He's being asked to fix problems that are outside his wheelhouse. He seems to be doing a bang-up job so far, finding SQL tools, etc that can find timing problems, etc. But ultimately this comes down to the code. Something that nothing short of time will allow the OP to learn well enough to solve the real issues.
He's already shown that the hardware is yawning - it's not busy at all (at least the stats we've been shown - for example, we haven't been told how deep the drive queues are).
I don't think tuning IIS apps as part of an IT person's typical job. That's a dev's job.
-
@Dashrender said:
@scottalanmiller said:
@jn19 said:
I've got full access to these machines but I have no software development experience, so I just want to do what I can to get things running more smoothly.
I'm not saying quit, but this is when you prep your resume and start looking. I'm not being funny in any way. It's impossible to read the situation from here, but everything that we are hearing is that you have completely incompetent developers and management and they are driving the product into the ground and throwing money away like crazy and are trying to blame IT for their failings.
I was thinking along these same lines.
It's harsh and I feel bad for how often this ends up being a suggestion but... often these questions come up because of situations that IT cannot fix and are endemic to the organization.
-
@Dashrender said:
I don't think tuning IIS apps as part of an IT person's typical job. That's a dev's job.
A little of both. But it looks like the issue here is all code, not IIS itself.
-
Very good points all around! And, to be honest, touching up the resume is definitely good advice at this point.
My boss (IT director) and I are in agreement about what needs to be done to move toward long-term success, scalability, and performance, so we hope to meet with our CEO, point out the application & IIS issues, and pitch a shift toward at least testing with PostgreSQL. If he agrees with the fact that these performance, code, and licensing problems are, and will only continue to be, huge yet surmountable issues that will make or break his company, then we'll let him know that we're happy to help with whatever we can. -
Just following up, how is everything going over there @jn19
