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.
File Size.
Marco_Savary
Member Posts: 12 ✭
Is there a way to see the file size of each document? Because, I only have 3 parts built so far, and I already used 32 megs. It seems large for 3 parts.
0
Comments
https://forum.onshape.com/discussion/comment/7323#Comment_7323
Indaer -- Aircraft Lifecycle Solutions
It seems that Onshape has a larger file size than a desktop cad, because is smarter and does more. Since is not my hard-drive and if Onshape become more powerful than desktop cad on a near future. Should we care about file size? Perhaps no.
I wonder if there is a time penalty to be paid in when downloading a large project from a fresh browser window?
"hamburger menu"?
Remember that any versions or share or external links to document won't work anymore but affect to file size can be signifigant.
I had document 114mb, took a copy and filesize wen't to 4mb then there was automatic update which raised file to 9mb.
I think it is a bit of problem for free user if limit is near and Ons pushes new updates which seem to have pretty big affect on file size..
"hamburger menu"?
I did this but the file size doesn't change and the history is gone. I have a VERY hard time understanding how the stuff I've been working on could be 99MB.
Ok, 5 minutes later the file size changes down to 1MB. Not sure why there is a 5 minute delay in updating the info.
This is a usability documentation problem. It would be good to add a help doc on this AND make it clear to users that "Copy Workspace" removes history. In addition to causing issues for users like me, I can see it causing issues for people who expect the history to be maintained. Put a checkbox that says "remove history" and have it checked by default.
Onshape remembers every action you took, not just the features in the tree. Yes, EVERYTHING (unless or until you purge the history, which should not be confused with the tree/list)
If you or anyone else strikes this behaviour again, it would be good to document the circumstances and report it using "Feedback"
1. When a user copies the current workspace to create a new document, we initially guess the document sizes are equivalent while calculating what the new document size is.
2. When a user uploads a file to create a document, we initially guess that the document size is the same as the file size. This can change depending on what is packaged in the file. For example, a PDF is very static content and the document size should be equal to the file size. An x_t file is extracted and creates part studio(s) and assembly(s) which can increase the document size.
What you are seeing is normal and the correct value should be reported within a couple of minutes. If you are not seeing that happen, please log a ticket and we'd be interested to investigate.
Great job on explaining that, thanks.
Looking through the user's end of the same telescope, the main situation where we take an interest in file size is when trying to reduce it.
And the usual tool, for the present, is "Copy workspace".
It would be rather more helpful to us, in this scenario, if the software, rather than pretending to know the file size prematurely, would report something equivalent to "CBS" ("check back soon").
The other main situation is when we're near our limit and uploading a large file, and (again) it would be preferable to be advised nothing, pending being advised something reliable.
If this cannot be done for some reason, I hope you would still find a way to address the previous scenario.
Perhaps another alternative for scenario one would be to separate the history size (which would be stripped out on copying the workspace) from the irreducible model data component, and report them in separate columns?
----------------------------------------------
It's not easy to respect limits when our indicator can be out by an order of magnitude.
Rewriting Help, as suggested by @robert_farrow , would at least allow discerning users to find out why they have a dodgy indication.
However, new (or forgetful!) users will first have to frustratingly discover the dodginess for themselves, in order for it to occur to them to check Help (or bug you one the forum) for the reason.
I do know there is more difficulty computing/reporting the storage of imported data as there is a certain unknown of what is stored in it. Data types that are translated have variable effect on how much the storage size will increase depending on their complexity and likewise take a variable amount of time to translate. Reporting the file size of the upload initially is what the size of the document is at that time, but it can change once the translation finishes.
Indaer -- Aircraft Lifecycle Solutions
Indaer -- Aircraft Lifecycle Solutions
Mark
After deleting 4 semi-important files, my one file kept creeping up to over my 100Mb limit. I'm a beginner and couldn't afford the $100/month (maybe I could pay one time $100). I was starting to think I'd have to abandon the whole project, until I saw this post. I just copied my workspace and my file dropped from 98Mb to 2Mb. Wow!
I wish I had seen it before I deleted the other "versions" of the project.
Thank you guys.