topic Re: SLOW UPLOAD AN CHECKIN in Windchill

SLOW UPLOAD AN CHECKIN

cspinelli — Fri, 06 Mar 2026 13:37:28 GMT

Version: Windchill 13.0

Use Case: For some users upload, checkin and every interation with Windchill from Creo are very slow

Description:

For some users upload, checkin and every interation with Windchill from Creo are very slow. even refresh of frames are real slow

Re: SLOW UPLOAD AN CHECKIN

avillanueva — Fri, 06 Mar 2026 13:58:36 GMT

Are you seeing this for just some users? If you can, post stats from event manager from the different sets of users. You want to eliminate variables like time of day or location. The biggest factor might just be the size of the workspace they are checking in from. The larger the workspace size, the slower it will be. In the past, use of very large and nested family tables (1000+ instances) had a dramatic performance hit, even if the instances were not all in the workspace.

Re: SLOW UPLOAD AN CHECKIN

cspinelli — Mon, 09 Mar 2026 07:46:32 GMT

yes, only for some users but in the event manager you can see nothing. in fact the workspace is big (>10k objects) but for other users its no problem.

Re: SLOW UPLOAD AN CHECKIN

avillanueva — Mon, 09 Mar 2026 10:45:04 GMT

Holy cow that is big! Do your users ever create new workspaces or clear them? That should be standard practice unless your assemblies contain 10K components. Large family tables have had significant impacts on performance regardless of workspace size.

https://community.ptc.com/t5/Windchill/Put-your-PDMLink-system-on-a-diet/m-p/482510

Re: SLOW UPLOAD AN CHECKIN

cspinelli — Mon, 09 Mar 2026 16:23:55 GMT

Our assemblies contains more than 10k objects indeed... in fact i checked and also with 5k objects upload and checkin are slowing down.

Re: SLOW UPLOAD AN CHECKIN

avillanueva — Mon, 09 Mar 2026 18:32:10 GMT

Well, the size will be a contributing factor but what about use of large family tables (1000+ instances)? Same rule applies for large assemblies. Make sure users clear their workspace from time to time. Unless you are working on top top level, no need to have entire thing in workspace. Also, recommend using simp reps. Just download assembly only. Then open a simp rep. Only what is required for that rep will download (thought a bit slower since retrieving as regenerating) but workspace will be smaller. models will be added as you switch reps. Clear periodically.