Kinetic Cloud SLOOOWWW to NON Responsive

Another company in Michigan also uses this offering from 2w and I checked in with them just yesterday on it to ask about stability specifically. They are also pleased with the stability and have only seen a few CPU spikes that they had to do something about. I will let them pop in here if they feel like sharing more.

Safe harbor here :safe_harbor: , the last time I talked to my CAM about this it seemed that this channel offering had changed in terms of who it’s allowed to be offered to and what the details of it are going forward into the future.

When did you move to this and what was that request like?

:safe_harbor: I also heard that if you need support it often is a pointing game between Epicor & 2W teams as they play hot potato with your issue on who’s responsible. That may have been worked out by now as it was months ago but something to ask if you’re considering this offering.

Question, for those on this, does the 2W offering have the Cloud Management Portal or something like it? It’s nice to be able to regen the DB when adding UDs, etc.

You get full access to the app server so it’s all yours to do whatever with in terms of admin console, logs, etc.

BUT, I think I was told in the future that goes away.

No, no access to app or db servers, no access to cloud management portal. Can’t even get read only SSMS access.

@Brandon_Stickel do you have access to your app server? I know that the other company does.

Our issue wasn’t a labor contingency plan, but the assertion by support that the problems were either fixed or they were our problem, and then responding to them that it wasn’t fixed, and then not hearing anything from them for hours/days at a time. It was the promise that things would be addressed in a particular way and in a particular timeframe, so we made labor decisions based on that. We were being told it was fixed, and we just need to try again. We had the subject matter experts in several departments trying to test Epicor’s fixes. Our major problem was that Epicor wasn’t down, according to support, yet it was, and it took lots of labor just to convince them that it was.

We don’t have access to the servers, for the most part. Through the Azure portal, we can see some statistics and real-time monitoring of the app server, which is nice. But in terms of restarts or making changes, that is out of our control. There is also no CMP.

For your earlier question regarding timing and discovery of the product. I checked my notes and we engaged the 2W sales team and our CAM in January. There was a lot of approvals on the Epicor side that needed to take place and it took many weeks before we actually started with the project. I’m not sure if there are any restrictions on who is eligible or not, that didn’t come up in our conversations.

As mentioned in some other comments, it hasn’t been all sunshine and rainbows. Although the performance and stability of the system is significantly better, the trade-off is that support really doesn’t know how to handle requests. 2W says to open an EpiCare ticket. Epicor says to open a 2W ticket (insert spiderman pointing meme). This can get frustrating trying to get things like data regens or restarts done.

Thanks for the info I know a lot of people have been wondering about this. I know it’s still not super clear, but hopefully this got people more detail than they had.

I’m afraid to report our PROD is super slow. Anyone else?

Not seeing it here - we weren’t part of the affected group yesterday either.
We got whacked on 7/24 and 7/31 though.

I’m sorry you’re dealing with this.

This is where our community speed test tool (that we all collaborate on and run via rest calls or whatever to represent things we believe are indicative of performance) could help us out.

Alisa had one she made, idk if we can get an Epicor-approved tool to monitor and track performance that would be cool.

Im going to be honest, its pretty hard for me to tell if Kinetic is being extra slow (server issues) or if Kinetic is being extra slow (poorly designed web pages), because its always slow for me. It takes 15-20 seconds to load an Order in Order Tracker, which is so goofy considering you can pull and load the data via the same api calls in about .1 seconds.

When I first started using classic I though it was slow, but I guess I didnt know it could get worse.

And I think Ive had a dozen or so SAAS outages in the past year that lasted long enough to impact the business. Its crazy how unreliable its been.

This just sounds like On Prem managed by consultants… of course it’s better than SaaS, but still not as good as On Prem managed by yourself :wink:

Most of the other major Epicor Partners offer private cloud hosting, whether it’s your private cloud that they just configure / manage for you (services + support) or it’s their infrastructure where they provision a server/db for you. But somehow 2W has a special deal with Epicor where they get to do the same thing but call it “Custom Cloud”… And if I’m not mistaken this offering is supposed to survive the death of On Prem in 2028… (this is all rumors and hearsay, I don’t know anything for sure)

It’s supposed to, but how exactly? They going to adopt whatever cloud architecture/deployment that Epicor is developing for?

Same issue-- seems like we are on the same pod/cluster or whatever. We both went down yesterday and we both have speed issues today.

Well, its not like On-Prem is dying because architecture. Its a business decision to ensure the subscription cashflow model. The cloud architecture/deployment is just the “justification” for it.

Only issue listed on the Epicor status site is Pilot maintenance in Singapore…nothing for Americas.

I could have been more clear perhaps, I was just wondering what 2w is going to migrate to so that they could continue keeping their cloud customers current with later versions and releases.

I know that on-prem isn’t dying because of architecture. We had a company running vantage 8 till last year… pretty sure they wouldn’t mind going back to it either- it worked fine for them in terms of functionality… Way more risk with operating system vulnerabilities and such, but the functionality worked fine for them.

The same thing. It all runs on Kubernetes so should be able to be spun up pretty much anywhere. 2W is just using the same server provider as Epicor anyways. Its just who is managing it that changes.

When I say on-prem isnt dying because of architecture, I dont mean as in you could run an older version . I meant that you could probably still have on prem with the newer versions if Epicor still had interest in allowing that, but from a business model perspective Epicor doesnt want to allow on prem.

Interesting question… how does Epicor actually kill On Prem when v2029.100 is released?

Well, I assume it won’t be available on EpicWeb for starters, but will they also build something into the code where it only works if there is some kind of check in with Epicors cloud servers?

Or is there still a semblance of hope for the hybrid container option (On Prem with subscription)??