"Øystein O. Johansen" <address@hidden>
wrote on 07/08/2007 09:47:10:
> Thank you! I'm on a single processor machine, so I can not test this
> here and now. I guess it's fine.
Actually, you can use the multi-thread exe on a single-proc
machine.
With the number of threads set to 1, it should behave
just like the single-thread exe. The only diff should be a small
overhead in the code, hence expect it to be slightly slower (I do think
it practically as fast, the difference is extremely small).
With the number of threads set to 2 or more, you will
be running multiple threads. With 2 threads on a 2 proc machine, the speed
almost doubles. Of course, on a single proc machine, the speed will
not change (or almost), but the multi-thread code must run even on a single
proc machine.
> > - The glib flavor crashes for me
>
> What's this? What crashes?
Under windows, the multi-thread code may use two different
thread libraries: the glib one and the windows one. The glib
one is the GNU one, the one used when compiling under Linux/Unix.
Windows one is windows specific.
When they both run, they seem to be just equivalent
in terms of performance, hence the goal would be to get rid of
the win-specific code and use glib threads all the time. The problem
is that the glib multi-thread exes do crash for me and despite Christian's
efforts we haven't been unable to solve the issue.