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

[Nick Renders]

Hi Stephane,

I would think that MacOS 10.8 has no problems with unicode.
I'll do some tests on a newer OS, see if the same thing happens
there.

Cheers,

Nick


On 23 Mar 2017, at 18:03, Stephane Pras wrote:

> Nick,
>
> I experienced the same kind of problem, but running Omnis Studio 
> 4.3.2.1
> (non-unicode) on Mac OS X 10.11.6. It fully disappeared after 
> upgrading to
> Omnis Studio 5.2.3 (unicode).
>
> It seems to be related to a slower dialog between software and OS X 
> when one
> is non-unicode and the other one unicode, probably because of some
> unicode/non-unicode translation needs. This is particularly obvious 
> when
> printing reports, which become tremendously long.
>
> Should be resolved if everybody is unicode, or everybody is 
> non-unicode.
> Meanwhile Š
>
> Stephane
>
> From:  omnisdev-en <omnisdev-en-bounces at lists.omnis-dev.com> on behalf 
> of
> Nick Renders <omnis1 at arcict.com>
> Reply-To:  OmnisDev List - English <omnisdev-en at lists.omnis-dev.com>
> Date:  Thursday, March 23, 2017 at 2:51 PM
> To:  OmnisDev List - English <omnisdev-en at lists.omnis-dev.com>
> Subject:  O$ 5.2.3: runtime slow after unicode conversion from O$ 4.3
>
> 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
>
> _____________________________________________________________
> Manage your list subscriptions at http://lists.omnis-dev.com
>
>
>
> _____________________________________________________________
> Manage your list subscriptions at http://lists.omnis-dev.com