O$ 5.2.3: runtime slow after unicode conversion from O$ 4.3

[Nick Renders]

Hi Doug,

We are using the V3 DAMs that came with O$ 5.2.3, not ODBC.

Nick


On 23 Mar 2017, at 15:06, Doug Easterbrook wrote:
>
> are you using the postgres dam?     or still through odbc?
>
> Doug Easterbrook
> Arts Management Systems Ltd.
> mailto:doug at artsman.com
> http://www.artsman.com
> Phone (403) 650-1978
>
>
>
>
> National User Conference, May 8-11, 2017
> https://tickets.proctors.org/TheatreManager/95/online&perf=27956
>
> On Mar 23, 2017, at 7:51 AM, Nick Renders <omnis1 at arcict.com> wrote:
>>
>> Hi,
>>
>> We recently updated our Omnis Studio 4.3.2.1 non-unicode library to
>> Omnis Studio 5.2.3 (unicode). We didn't need to make any changes to
>> the library's code as we had already made all the necessary
>> preparations in Studio 4.
>>
>> The library is now run on the same machines as before (most of which
>> are running MacOS 10.8.5), only now they are using the Omnis Studio
>> 5.2.3 runtime. We connect to the same ODB and Postgres databases
>> as before.
>>
>> But for some reason, the library (or rather the runtime) slows down
>> after some time using it. It feels like there is some memory leak
>> causing it, because when you quit the application and relaunch,
>> everything is back OK.
>>
>> Does anybody have a similar experience? Any clue what might be
>> causing this?
>>
>> My first thought was: object instances. We use a bunch of them, but
>> had no performance issues in Studio 4. Has anything changed between
>> Studio 4 and 5 on how objects are handled?
>>
>> My second thought was: externals. Again, we use a bunch of them, and
>> obviously they are not exactly the same (unicode vs non-unicode).
>> But my tests don't show any performance decreases when I only use
>> the externals.
>>
>>
>> Best regards,
>>
>> Nick Renders