Omnis Data Bridge speed
I would leave Omnis Native behind but the conversion to SQL is just too big a job.
> On Oct 1, 2017, at 9:36 PM, sethpaien <firstname.lastname@example.org> wrote:
> Which ODB version is used ?
> In 1.62 release notes :
> Windows. Omnis Data Bridge is limited to a maximum of 2048 file
> handles on Windows. This limit has been removed by switching to a
> different file API.
> We face down this problem so we try to use this version, it works, but
> too much slowly than before, so we rollback to previous version.
> I haven’t try newer version and don’t know if performances have been improved,
> never submitted this performance issue cause it’s maybe the time to
> leave an “old or obsolete technology” (to quote omnis website)
> 2017-10-01 12:38 UTC+02:00, Marc De Roover <email@example.com>:
>> We are using an 6 drive Raid-6 system on our server and feel this is a
>> good solution:
>> – many spindles increase data access speed
>> – fault tolerance due to Raid-6
>> A better solution would be to usz a ZFS based system, since it would
>> also protect data integrity.
>> PS: could your speed issue be related to single-user vs multi-user mode
>> On 29 Sep 2017, at 23:25, Ben Weinberg wrote:
>>> I’m running ODB on a Windows 2008 server and, for testing, I
>>> compared the speed of building a list using ODB and then using the
>>> same Omnis Native datafile locally on my Mac. The list takes 46
>>> seconds to build on the server but 2 seconds to build on my Mac.
>>> While this is consistent with my results over previous tests, I wonder
>>> if there is a way to speed ODB up? Network and switches are 1000Gb.
>>> Ben Weinberg
>>> Manage your list subscriptions at lists.omnis-dev.com
>> Manage your list subscriptions at lists.omnis-dev.com
> Manage your list subscriptions at lists.omnis-dev.com
Manage your list subscriptions at lists.omnis-dev.com