Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.
First time visiting? Here are some places to start:- Looking for a certain topic? Check out the categories filter or use Search (upper right).
- Need support? Ask a question to our Community Support category.
- Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
- Be respectful, on topic and if you see a problem, Flag it.
If you would like to contact our Community Manager personally, feel free to send a private message or an email.
Slow Document Performance: Is Anyone Else Experiencing This?
JamesonBinanitan
Member Posts: 20 PRO
Hi Everyone,
I'm based in Asia and collaborating with European colleagues. For over a month, we've been facing performance issues with our documents. When a European colleague creates a document and I try to access and edit it, the document responds slowly, especially when using features like variables and mates. Sometimes, even opening the document takes an excessive amount of time.
This issue occurs reciprocally when I create a document and my European colleagues attempt to access it.
I've already submitted a ticket about this, but the recent update hasn't resolved the problem.
This was not an issue before, so I'm puzzled as to what might have caused it.
I'm curious if anyone else is experiencing this problem or if it has been resolved for anyone. If you've found a solution, I'd appreciate hearing about it. Alternatively, are there any workarounds or alternative approaches that you've found helpful?
Answers
Does this happen with a new simple document or is it more of an issue with a complex document with a lot of features and dependencies within the document (derives, in context, etc)? I would eliminate any document related issues first.
My experience (based in California) working with a colleague in China was that there were definitely times where initial document access was slow. My understanding is that behind the scenes documents literally live on a particular AWS server, and they get copied when you access them in a different region. This can sometimes be slow. Once this happens, performance should improve. I also notice some weird performance issues around the time that each new update is released every three weeks (or so).
I hope you get some useful feedback from support.
It's not what you're doing. Somethings going on with service, this is rare.
status
well, that was fast, it's up
Having the same issues here.
I've also observed a consistent decline in speed/responsiveness, starting almost 4 years ago. It's been particularly bad this last two weeks, and it was out entirely this morning.
What originally brought me to OnShape was the ability to open any assembly on any machine without issues. I used to be able to open anything without regard to part count or complexity. Now I have a document with a single part studio with 3 assemblies and 8 drawings; it often hangs on loading (eg shows the loading wheel until it times out)
@john_mcneil707
I've been using OS for a long time and think it's pretty reliable. Last time I remember it was down was during the AWS dns hack, but that was a long time ago.
I'm not sure why your system is slowing down and you might want to try crl-d to check your ping rate.
I'm working on a good size assembly and I'm enjoying it.
We definitely had an outage today. Onshape was slow and then down for a total of about 47 minutes. Our status page, https://status.onshape.com, is always the place to go when you are trying to answer the "Is it me or is it Onshape?" question.
https://status.onshape.com/incidents/ynn5j3nf81xb
@JamesonBinanitan, I am aware of the issue you have reported and we are working to understand it. Sorry for the hassle.
@john_mcneil707, we've pretty consistently improved the performance of Onshape with almost every release. A decline in speed / responsiveness over 4 years is not expected. Please open a support ticket.
@S1mon, @john_mcneil707 thank you for sharing your experiences. In our case, the issue is noticeable in documents with variable studios. This started after the release update in July. I didn't pay much attention to it back then, as I assumed it might take a week for performance to improve.
@billy2
@john_rousseau
@ , I understand. Thank you for assuring us that you're working on it. I posted here in the forums because we're curious if other users are experiencing the same issue, and we hope to receive positive feedback. We're currently exploring temporary solutions to improve our current workflow. @thank you so much for sharing the "status" link. This is new to me.
(I'm not sure what happened to my initial comment; I lost the text view and couldn't edit it.)
@S1mon, @john_mcneil707 thank you for sharing your experiences. In our case, the issue is noticeable in documents with variable studios. This started after the release update in July. I didn't pay much attention to it back then, as I assumed it might take a week for performance to improve.
@billy2 thank you so much for sharing the "status" link. This is new to me.
@john_rousseau I understand. Thank you for assuring us that you're working on it. I posted here in the forums because we're curious if other users are experiencing the same issue, and we hope to receive positive feedback. We're currently exploring temporary solutions to improve our current workflow.