Yes, I know that - and that's why I'm asking about outcome of this - which I THINK is that the OS will assign a process to a free core and make it parallell to the processes that currently run at the first core. And this will result in parallell execution of processes (if there are no different circumstances - like file locks, I've mentioned).Eddi wrote:distributing processes/threads onto multiple cores happens in a lower layer of the OS, which neither MSVC nor GCC can and will care about.lukasz1985 wrote:Isn't this a case for GCC?
Debug build low performance.
Moderator: OpenTTD Developers
-
- Route Supervisor
- Posts: 429
- Joined: 27 Mar 2013 08:58
- Location: Strumien
- Contact:
Re: Debug build low performance.
Last edited by lukasz1985 on 23 Sep 2015 18:19, edited 1 time in total.
Re: Debug build low performance.
yes. both threads and processes are methods of parallelisation, but processes are more independent than threads, which can share memory (with all sorts of accompanying problems) [simplified description]
-
- Route Supervisor
- Posts: 429
- Joined: 27 Mar 2013 08:58
- Location: Strumien
- Contact:
Re: Debug build low performance.
Ahh.. ok, I get it, I was making wrong conclusion from what @JGR said - that multi-process prevents parallelisation.
Re: Debug build low performance.
Nah, just set a sane default in your shell init script:JGR wrote:you need to pass -j to make
Code: Select all
export MAKEFLAGS=-j4
Being a retired OpenTTD developer does not mean I know what I am doing.
Re: Debug build low performance.
I don't know if they do, but they can (to some point): Linux, Windows, OpenMP, MPI...Eddi wrote:distributing processes/threads onto multiple cores happens in a lower layer of the OS, which neither MSVC nor GCC can and will care about.
don't worry, be happy and checkout my patches
Who is online
Users browsing this forum: No registered users and 14 guests