$O OW3 - multiple http/ftp workers with $start on background thread

[Doug Easterbrook]

Hi Ben.

The worker concept is a part of Studio now and seems to have been implemened the same throughout database threads ow3 workers.


Each OW3 worker sparks an instance of CURL — so it its curl that does all the work on its own thread.    there is no reason to believe that you can’t start more than one if you have separately instantiated objects.


when we first demonstrated the postgres worker object concept at Euromnis a lont time ago, we sparked up 64 threads to obtain data from a database.   The only reason we stopped at 64 was arbitrary.     and eventually you run out of total CPU on your machine to make them all work efficiently.      it was kind f fun maxing out a 4 core machine.



Doug Easterbrook
Arts Management Systems Ltd.
mailto:doug at artsman.com
http://www.artsman.com
Phone (403) 650-1978

> On June 11, 2020, at 3:53 AM, Ben Butler <760.f563 at gmail.com> wrote:
> 
> Hi All,
> 
> Quick question, is there a single background thread that is owned by Omnis
> at Dev / RT level, or, does each OW3 worker create a new background thread
> for that instance?
> 
> Say I start one ftp worker off downloading a large file, control gets
> returned to the foreground after start - say a now create another instance
> of an ftp worker object and try to set it off downloading another large
> file launched with $start again rather than $run - does it collapse in a
> heap or do we end up with two worker object instances happily downloading
> each on their own background thread?
> 
> Thanks in advance for your thoughts...
> 
> Ben
> _____________________________________________________________
> Manage your list subscriptions at http://lists.omnis-dev.com
> Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com