All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <20170316135122.GF13054@aaronlu.sh.intel.com>

diff --git a/a/1.txt b/N1/1.txt
index 88a6c7b..b40e1e1 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -18,26 +18,20 @@ On Thu, Mar 16, 2017 at 03:34:03PM +0800, Aaron Lu wrote:
 Here are test results on 2 nodes EP with 128GiB memory, test size 100GiB.
 
 max_active           time
-vanilla              2.971s +-3.8%
-2                    1.699s +-13.7%
-4                    1.616s +-3.1%
-8                    1.642s +-0.9%
+vanilla              2.971s ±3.8%
+2                    1.699s ±13.7%
+4                    1.616s ±3.1%
+8                    1.642s ±0.9%
 
 So 4 gives best result but 2 is probably good enough.
 
 If the size each worker deals with is changed from 1G to 2G:
 
 max_active           time
-2                    1.605s +-1.7%
-4                    1.639s +-1.2%
-8                    1.626s +-1.8%
+2                    1.605s ±1.7%
+4                    1.639s ±1.2%
+8                    1.626s ±1.8%
 
 Considering that we are mostly improving for memory intensive apps, the
 default setting should probably be: max_active = node_number with each
 worker freeing 2G memory.
-
---
-To unsubscribe, send a message with 'unsubscribe linux-mm' in
-the body to majordomo@kvack.org.  For more info on Linux MM,
-see: http://www.linux-mm.org/ .
-Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
diff --git a/a/content_digest b/N1/content_digest
index 3924892..839ea4e 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -35,28 +35,22 @@
  "Here are test results on 2 nodes EP with 128GiB memory, test size 100GiB.\n"
  "\n"
  "max_active           time\n"
- "vanilla              2.971s +-3.8%\n"
- "2                    1.699s +-13.7%\n"
- "4                    1.616s +-3.1%\n"
- "8                    1.642s +-0.9%\n"
+ "vanilla              2.971s \302\2613.8%\n"
+ "2                    1.699s \302\26113.7%\n"
+ "4                    1.616s \302\2613.1%\n"
+ "8                    1.642s \302\2610.9%\n"
  "\n"
  "So 4 gives best result but 2 is probably good enough.\n"
  "\n"
  "If the size each worker deals with is changed from 1G to 2G:\n"
  "\n"
  "max_active           time\n"
- "2                    1.605s +-1.7%\n"
- "4                    1.639s +-1.2%\n"
- "8                    1.626s +-1.8%\n"
+ "2                    1.605s \302\2611.7%\n"
+ "4                    1.639s \302\2611.2%\n"
+ "8                    1.626s \302\2611.8%\n"
  "\n"
  "Considering that we are mostly improving for memory intensive apps, the\n"
  "default setting should probably be: max_active = node_number with each\n"
- "worker freeing 2G memory.\n"
- "\n"
- "--\n"
- "To unsubscribe, send a message with 'unsubscribe linux-mm' in\n"
- "the body to majordomo@kvack.org.  For more info on Linux MM,\n"
- "see: http://www.linux-mm.org/ .\n"
- "Don't email: <a href=mailto:\"dont@kvack.org\"> email@kvack.org </a>"
+ worker freeing 2G memory.
 
-47b47c88fcdb4dddf07bfb961a46ba263aec24bf335630ed9d8d327564f67484
+7a94cbf48c7fe016d673a09b057eb1dd6db4314863a506fce5bd8b684297a308

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.