What could make the published Content Center filesize large?

[karthur1]

I have an ipart family that has a huge table in it.  It takes several minutes to place these in my assemblies.  I thought I would publish this to the content center, since this is the suggestion to speed things up.  I published the part and it is much faster to place the part in my assembly.

When I compare the filesize of the ipart child to the content center part, there is a huge difference.  I did not make any edits when I published the part to the CC.  The filesize of the ipart child is 201.5KB.  The same part published to the content center is 1,036 KB.

I used an alternate thumbnail when I published the part, but it is only 43kb. I like to keep the filesize to a minimum if possible.  What could make this so large?  

Thanks,

Kirk

[Mark.Lancaster]

@karthur1

I've never compared a iPart child file size to a content center published component but I think the difference you're seeing is the way an iPart child is made.  Meaning that an iPart child has limited stuff since it gets all of its information from the iPart factory where-as the content center is more closer to the iPart factory which is containing all of the information. In the end the information internally (that you can't see) has a lot more in one file compared to the other.

[PaulMunford]

I think Mark is right. Are we right in saying that you are comparing the size of the iPart factory with a member generated by content center?

To make an equal comparison you would need to compare a member file generated by the iPart factory with a member generated by content center.

There is no way to compare the size of the iPart factory with the size of the content center family, unless you measured the size of the content center database before and after you publish the iPart factory to the content center?

Interesting question. Keep us up to date with your findings 😉

[johnsonshiue]

Hi Kirk,

This is an interesting observation. I was not aware of the difference either. Please feel free to send me the files directly ([email protected]). I can use internal tool to tell what the additional storage is and if it is behaving as expected.

Many thanks!

[karthur1]

Johnson,

I did try a simple test where I made an ipart with about 5 rows and generated the children.  Then I published the same ipart to the CC.  The filesize of the CC parts was slightly larger (140KB) compared to the ipart children (100KB).  I will get the files together and get them to you.  Will probably be tomorrow.

Thanks,

Kirk

[PaulMunford]

Great Job @karthur1 😄

[karthur1]

Just to follow-up on this:

I sent the files to Johnson and he looked at them.  He came back and said that the CC files are basically the iPart parent file minus the table.

The iPart parent is about 1820kb and the CC parts come in around 1036kb.  If I remove the table from the ipart it is 976kb, which is slightly under the CC parts.  The ipart members are much more compacted than the CC parts.