瀏覽代碼

Revert "Work in progress: Add new [Setup] section directive LZMANumBlockThreadGroups - just the documentation so far."

This reverts commit c1485c2c4ba76eba94aad111226fe55f840f751e.
Martijn Laan 3 天之前
父節點
當前提交
0ceb47c6be
共有 2 個文件被更改,包括 2 次插入15 次删除
  1. 1 14
      ISHelp/isetup.xml
  2. 1 1
      whatsnew.htm

+ 1 - 14
ISHelp/isetup.xml

@@ -998,7 +998,6 @@ DefaultGroupName=My Program
 <li><link topic="setup_lzmablocksize">LZMABlockSize</link></li>
 <li><link topic="setup_lzmadictionarysize">LZMADictionarySize</link></li>
 <li><link topic="setup_lzmamatchfinder">LZMAMatchFinder</link></li>
-<li><link topic="setup_lzmanumblockthreadgroups">LZMANumBlockThreadGroups</link></li>
 <li><link topic="setup_lzmanumblockthreads">LZMANumBlockThreads</link></li>
 <li><link topic="setup_lzmanumfastbytes">LZMANumFastBytes</link></li>
 <li><link topic="setup_lzmauseseparateprocess">LZMAUseSeparateProcess</link></li>
@@ -6251,19 +6250,7 @@ SignTool=byparam format c:
 <p>Dividing the data into multiple blocks can reduce the compression ratio, as the compressor cannot find matches across blocks. Using a large <link topic="setup_lzmablocksize">block size</link> can help to mitigate this.</p>
 <p>If an "Out of memory" error is seen when multiple block threads are enabled in combination with a compression level that uses a large dictionary size (such as <tt>ultra64</tt>), <link topic="setup_lzmauseseparateprocess">LZMAUseSeparateProcess</link> may need to be set.</p>
 <p><b>See also:</b><br/>
-<link topic="setup_lzmablocksize">LZMABlockSize</link><br/>
-<link topic="setup_lzmanumblockthreadgroups">LZMANumBlockThreadGroups</link></p>
-</body>
-</setuptopic>
-
-<setuptopic directive="LZMANumBlockThreadGroups">
-<setupvalid><tt>1</tt> through <tt>4</tt></setupvalid>
-<setupdefault><tt>1</tt></setupdefault>
-<body>
-<p>Controls the ability of the LZMA2 compressor to distribute its threads across multiple processor groups:</p>
-<p>On Windows systems with more than 64 logical CPU cores, the operating system divides the CPUs into processor groups, each containing up to 64 logical processors. By default, all threads are assigned to a single group, which means that even if you create more than 64 threads, only 64 can run in parallel on separate cores. To actually utilize additional cores beyond the first 64, one must explicitly distribute threads across multiple processor groups.</p>
-<p><b>See also:</b><br/>
-<link topic="setup_lzmanumblockthreads">LZMANumBlockThreads</link></p>
+<link topic="setup_lzmablocksize">LZMABlockSize</link></p>
 </body>
 </setuptopic>
 

+ 1 - 1
whatsnew.htm

@@ -203,7 +203,7 @@ Source: "https://jrsoftware.org/download.php/iscrypt.dll?dontcount=1"; DestName:
     </ul>
   </li>
   <li><tt>[Files]</tt> section parameter <tt>Excludes</tt> can now be combined with the <tt>external</tt> flag.</li>
-  <li>Increased the maximum value of <tt>[Setup]</tt> section directive <tt>LZMANumBlockThreads</tt> from 32 to 256, and added new <tt>[Setup]</tt> section directive <tt>LZMANumBlockThreadGroups</tt>.</li>
+  <li>Increased the maximum value of <tt>[Setup]</tt> section directive <tt>LZMANumBlockThreads</tt> from 32 to 256.</li>
   <li>Parameters <tt>ExternalSize</tt>, <tt>ExtraDiskSpaceRequired</tt>, and <tt>UninstallDisplaySize</tt> now support digit separators. Example: <tt>UninstallDisplaySize=1_073_741_824</tt>.<br/>
       The same applies to <tt>[Registry]</tt> parameter <tt>ValueData</tt> if <tt>ValueType</tt> is set to <tt>qword</tt>.</li>
   <li>ISPP changes: