I'm very noob using UPP but i think this platform is really amazing.
I wrote this post because i have a doubt about CoWork; Its CoWork some kind of IOCP implementation?.
As you can know I/O completion port is an asynchronous mechanism provided directly by the OS kernel to manage I/O request. This technique y very efficient to manipulate thousands of clients in an client-server architecture.
How it works this mechanism is very similar to the work of CoWork (only a few threads to handle many operations), so for this reason i have this doubt.
I'm very noob using UPP but i think this platform is really amazing.
I wrote this post because i have a doubt about CoWork; Its CoWork some kind of IOCP implementation?.
As you can know I/O completion port is an asynchronous mechanism provided directly by the OS kernel to manage I/O request. This technique y very efficient to manipulate thousands of clients in an client-server architecture.
How it works this mechanism is very similar to the work of CoWork (only a few threads to handle many operations), so for this reason i have this doubt.
thx in advance.
Not really. It is basically a loop parallelizer.
If you are performing loop and each iteration is independent (or mostly independent) from other, you can use CoWork to spread the work across all CPU cores.
In fact, in processing intensive code, it is often enought to parallelize a couple of loops where it is possible and you get app using multicore CPU nicely.
Note that CoWork does not solve sharing problem - if you share any data between loop iterations, you have to synchronize access as usual (using Mutex etc...)
ohh, ok, i completly wrong about this issue. So CoWork is similar to OpenMP, right?.
I want to write a IOCP implementation using UPP, but is very difficult to me make it without the proper socket documentation. So i have to wait until this docs are available.
Members
Pages
Help
Register
Login
Home
