Karakun Support Forums

We use applications that consist of about 270 jars that need to be loaded. Starting with Oracle Webstart takes only a few seconds. With Openwebstart it can take up to 10 minutes. For individual users it is faster (about 1 minute), but not always.
Network problems should not be present.
We have tried to increase the parameter "deployment.cache.parallelDownloadCount". This gave a partial improvement, but it still takes way too long. Sometimes you get the impression that everything is still downloaded very slowly one after the other.

What can we do to improve this?

OWS uses different code from Oracle JWS hence will behave differently.

We have tried to improve download and it happens in parallel. deployment.cache.parallelDownloadCount will increase the number of download threads. Default is 6. Do you see the download dialog with progress bar for each jar?

Yes, the progress bar is displayed for each jar.

I cannot really say why the download is slow.

Are the logs you have sent by mail for the same application which you feel is slow while downloading? The logs indicate that there are 274 jar files.

From the stage-2 logs I can see that jar processing starts at 6:19:50.498 (line119) and jars are found in cache at 6:21:01.496 => about 2 minutes to download.

Yes, it is the same application. But it also applies to other applications that have the same base. For other users, the download time is much longer than 2 minutes.

Is there anything else I can do here now?

You have tried increasing download threads. Beyond this it is hard to say how OWS is performing in on in your environment. We need to do detailed profiling to observe the performance. Request you to buy paid support so that we can allocate dedicated resources to investigate this issue.

The current content of the local ows-file-cache is a relevant factor. Starting an application took over 25 Minutes (!). Cleaning file cache with on board functions in ows seems not to work (perhaps because of to much content?). After deleting the cache files with os system commands the start of the same application took about 2 Minutes.

Do you mean to say clearing cache with the itw-settings tool did not clear the cache?

Also do you mean that App started faster when cache was clean and OWS downloaded resources against when the resources were in the cache?

Is the app starting slow everytime when resources are present in the cache? I.e. you clean the cache, run the app with OWS, OWS downloads resources and it takes 2 minutes. You run the app again with downloaded resources in the cache and the app takes 25 minutes to start!

Yes, the itw-settings-tool seems to be overextended when cache has a huge content.

It looks like, it takes more and more time to start/update an application in relation to the current size of the content of the cache. It takes long not at second time, but when days and weeks go by, and the cache gets bigger and bigger, the applications are updating slower and slower. I'm talking about applications with many jars, don't know how it is on applications with only one jar.

Just to clearly identify your issues:

1. When there are many files in the cache itw-settings is not able to clean the cache, you had to do it at OS level.
This happened when you had 270 jars in the cache. How did you try to clean the cache, by selecting and purging files in "View Files" panel or "cleaning files by app"?

2. You clean cache and run jnlp with OWS. 270 files are downloaded and cached and then the app is started. How long does it take?

3. You run the app again. App is started from cache, nothing is downloaded. How long does it take?

4. You work with the app for one week. After one week or so the app starting from cache take 25 minutes? There is no download as the app is working from cache.