Performance tip - $root.$prefs.$maxCacheClasses

[Sten-Erik Björling]

Hi all,

Thanks for the tip.

Another tip that can be useful for those of us who are developing web apps etc. is to set the timeslice value down from 20 to 1 or 2. A timeslice value of 20 means that an task will take a minimum of one third of a second ( a tick is a 60th of a second ) and this will hamper app and web services servers a bit since most operations in an optimized Omnis application will take significantly less.

$root.$prefs.$timeslice

Stene

______

> 22 dec 2014 kl. 05:06 skrev Doug Easterbrook <doug at artsman.com>:
> 
> hi all:
> 
> I was playing around with our Omnis Studio library on the weekend - which has some 3000+ classes in it.   It performs really well, but I hit a small snag trying to make it perform well under the scenario where the library was not on the same drive as the application…   There is a reason that I want the library on a server (macintish - network user situation)
> 
> performance went down - dismally.
> 
> and then I discovered my saviour — a preference that can be set at run time.
> 
> 
> $root.$prefs.$maxCacheClasses
> 
> 
> initally it was set to 300 (as it has been for years)…. and so I set it up at 5000 - just for giggles.      After the initial load of my library by the omnis runtime, I got a bunch of performance back because more of the classes are being stored in ram.
> 
> so if you are not aware of this setting — its worth knowing.
> 
> you can also look at
> sys(190) - to see the number of classes loaded by the runtime and
> sys(191) - to see the number of classes discarded out of cache
> 
> 
> its really a lot faster if your app is not discarding classes out of the cache because $root.$prefs.$maxCacheClasses is set too low.
> 
> 
> thats my learning for the weekend.   hope it helps somebody.
> 
> 
> 
> 
> 
> Doug Easterbrook
> Arts Management Systems Ltd.