[ Date Index ]
[ Thread Index ]
[ <= Previous by date /
thread ]
[ Next by date /
thread => ]
[LUG] make -jn
- To: Devon/Cornwall GNU LUG <list@xxxxxxxxxxxxx>
- Subject: [LUG] make -jn
- From: Tom <madtom1999@xxxxxxxxxxxxxx>
- Date: Sun, 22 Feb 2015 21:16:17 +0000
- Delivered-to: dclug@xxxxxxxxxxxxxxxxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=dcglug.org.uk; s=1412586362; h=Sender:Content-Type:Content-Transfer-Encoding:List-Subscribe:List-Help:List-Post:List-Unsubscribe:List-Id:Reply-To:Subject:To:MIME-Version:From:Date:Message-ID; bh=WVEDvbIiUYtOMeo5NfyxEm3r7cv/nB24Vscv+cs4We0=; b=fnHVPZfmdMTkUlkeGCDmxB9tLWpqg0Fx3Pj+IJaDImaLm3sqeJiprVoZDwiiGn3W77APLx25Pk7NuaohTG1D942FNImFnkC6TuT0te8DWn1XzewZwKtptZfQ6VRfJBk+4jimaz72jnUycUETl7pL7ygilCqksEzbSvbChi0qdP4=;
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=emAj9nNTfCYTV3rj8pXk7uNadUUfkzhI3r34EFFB570=; b=KTpdeMeXhS75i7LM40lWk6HqiWaDu+a3E1+CTdgdLGpaUaf1TvUXhaS8XJBubcuz6U LmLaJuf/HeYmkIzCRKPabTahcPUGYLwHvpAkdcikcaCIfRG5/DPBPDVfYF0StvBaiWqs gBG9mH/xPgLrTIAvQUfS0Zyenh74vp2s3na5vK1RZscRFspxYHUiT7NVBIXTg87WmWZk /ZtXXk5AYYJtYN57NSlhlfG08K5ZmyiP/ew53XbwztcbqsjwsnsaCqtx5dGSqKXL6Oqw sz+0rd8zSn8jWo8+Y8J7NJJiP5/BUmqrxdlBllVy41vhGl5y4IJ7TY/MS0epcG7VtD3L mVTA==
Wot with all these multiprocessor jobies about these days I've been
trying to find a valid reason for choosing make -j(n+1 or 2) where n is
the number of cores. I've not been able to find anything 'scientific'
just suggestions that adding one or two to the core count may allow for
some of the tasks waiting for io to be replaced with other tasks but
that's wishful thinking rather than 'good software engineering'.
Anyone know different or how to test a running program so the value can
be optimised?
Tom te tom te tom
--
The Mailing List for the Devon & Cornwall LUG
http://mailman.dclug.org.uk/listinfo/list
FAQ: http://www.dcglug.org.uk/listfaq
