Forums

by cnwjhp1 >> Mon, 29 Oct 2007 1:04:52 GMT

Is serverExecution involved? Passing large amounts of transients back and forth can use up that amount of time, and serverExecution is ignored in SingleUser mode.

Even if you used the same ini file (did you?), running the app in singleUser mode vs thin client uses different sections of the ini file. And if serverExecution is involved in thin client mode, RemoteTransientCache could be involved also. Transient or persistent cache size in each relevant section could be the issue.

by John Munro >> Fri, 2 Nov 2007 18:23:15 GMT

Is serverExecution involved? Passing large amounts of transients back and forth can use up that amount of time, and serverExecution is ignored in SingleUser mode.

Yes, I added serverExecution to try to speed it up, I'll take it off and see if it makes any difference

Even if you used the same ini file (did you?), running the app in singleUser mode vs thin client uses different sections of the ini file. And if serverExecution is involved in thin client mode, RemoteTransientCache could be involved also. Transient or persistent cache size in each relevant section could be the issue.

Yes, it's using the same ini file, here are the relevant settings:


Thanks,

John

by John Munro >> Fri, 2 Nov 2007 18:25:50 GMT

Is serverExecution involved? Passing large amounts of transients back and forth can use up that amount of time, and serverExecution is ignored in SingleUser mode.

Yes, I added serverExecution to try to speed it up, I'll take it off and see if it makes any difference

Even if you used the same ini file (did you?), running the app in singleUser mode vs thin client uses different sections of the ini file. And if serverExecution is involved in thin client mode, RemoteTransientCache could be involved also. Transient or persistent cache size in each relevant section could be the issue.

Yes, it's using the same ini file, here are the relevant settings:

[JadeClient]
ObjectCacheSizeLimit=50M
TransientCacheSizeLimit=50M

[JadeServer]
ObjectCacheSizeLimit=50M
TransientCacheSizeLimit=50M
RemoteTransientCacheSizeLimit=20M

[PersistentDb]
ObjectCacheSizeLimit=100M

[JadeInterpreter]
MethodCache=Single
MethodCacheLimit=100M
StringPoolLimit=50M

I thought they were OK, but let me know if you spot any problems.

Thanks,

John

by cnwjhp1 >> Mon, 29 Oct 2007 1:05:48 GMT

Did you check the size of the transient overflow files during the runs?