Component load times.
3 answers
Load time depends on network and CPU of client machine. Does client access RTC remotely WAN with latency over 10 msec ? In a WAN environment, there is contents cache solution using squid.
https://jazz.net/library/article/325/ to increase load time.
Also, RTC client preference "maximum number of threads" for contents transfer may help.
If it did not help, I recommend go though trouble shooting section.
https://jazz.net/wiki/bin/view/Deployment/PerformanceTroubleshooting
https://jazz.net/library/article/325/ to increase load time.
Also, RTC client preference "maximum number of threads" for contents transfer may help.
If it did not help, I recommend go though trouble shooting section.
https://jazz.net/wiki/bin/view/Deployment/PerformanceTroubleshooting
Maybe you put too much files into component.
According to the following document, they recommend 100K files and folders in a single component.
Hi Mahari,
It could be great to gather basic information to narrow down the issue.
1. Are you able to reproduce the issue at the time when you get the complain? Or the issue is gone then?
2. Does it happen for all components or for any special ones? What is the difference between components having the issue and these not having the issue?
3. When did you observer long component load time first? What were particular operations you had performed before that (e.g. added new users to the system, added new components, added files to the components, added new service on the server, checked network device, any operations on database server etc.)
4. Do you observe any daily/weekly dependencies when the issue e.g. issue happens at ceratin time of the day, in certain days of the week etc.
5. Do you observer any trend in frequency of the issue, time to load component or the number of the components?
I know that there are many questions but it will be really great to narrow the issue :)
In the support we use Wait tool: https://wait.ibm.com/
You can enable it on the server to check what is exactly going on the server when the issue happens.
Best regards,
Chris.
It could be great to gather basic information to narrow down the issue.
1. Are you able to reproduce the issue at the time when you get the complain? Or the issue is gone then?
2. Does it happen for all components or for any special ones? What is the difference between components having the issue and these not having the issue?
3. When did you observer long component load time first? What were particular operations you had performed before that (e.g. added new users to the system, added new components, added files to the components, added new service on the server, checked network device, any operations on database server etc.)
4. Do you observe any daily/weekly dependencies when the issue e.g. issue happens at ceratin time of the day, in certain days of the week etc.
5. Do you observer any trend in frequency of the issue, time to load component or the number of the components?
I know that there are many questions but it will be really great to narrow the issue :)
In the support we use Wait tool: https://wait.ibm.com/
You can enable it on the server to check what is exactly going on the server when the issue happens.
Best regards,
Chris.