It's all about the answers!

Ask a question

RTC impact of uploading large files to SCM


Don Max (2411734) | asked Mar 23 '19, 11:22 a.m.

  We are having a distributed architecture and using Websphere base 8.5.5.14 and DB2 database along with IHS. Also webcontainer write property is set sync mode for RTC WAS profiles. We have noticed that some of our teams are uploading large files of 3GB and more to RTC (CLM 6.0.6) scm.Does uploading such files impact the overall perfromance of the application considering our teams are using heavily for scm. Will it impact other clm application users considering the load on IHS.?

Am aware of the external content reporsitory option but we are yet to use this. Also does this option improves application performance.

Thanks
Don

2 answers



permanent link
misha rajpoot (341) | answered Mar 25 '19, 5:42 a.m.

 uploading of large file is not a good way of loading the file because loading of large file will take a large amount of time and it can also happen that if any single file fail to upload so we have to cancel the whole file and have to again upload it.


permanent link
Ralph Schoon (63.7k33648) | answered Mar 25 '19, 3:17 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

Uploading a 3GB file in an SCM system is not a good idea. Use a binary external content repository such as Artifactory integrated with RTC. 


Comments
Don Max commented Mar 25 '19, 5:07 a.m.

Thanks Ralf. 


Could you please give a couple of points why its not a good idea to upload large files. This will help us to push the management for the external repository solution.



1
Ralph Schoon commented Mar 25 '19, 7:23 a.m. | edited Mar 25 '19, 7:23 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

Don, RTC stores SCM data in a database. It has to store binaries in the database as well. Databases are not ideal to store huge data, let alone binaries. All the data has to be passed through the involved servers as well. If a server is already busy, this makes things worse. We suggest using caching proxies, that can help to some extend.


The big files bloat the database footprint and you ideally want to avoid this. The bigger the database gets the harder maintenance and backup becomes etc...

As long as I am involved, we have told users that they should not check in huge binaries. There are even limits you can enable since a long time. There are users that created extensions that prevent their users checking in binaries with  rule sets etc.

So, use the new large file storage capability. As far as I know it actually moves big files over that have been checked in in the past. The users should not even notice the new feature.  

  

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.