summaryrefslogtreecommitdiff
path: root/open_issues/crashes_vs_system_load_cpu_load_rpc_load.mdwn
diff options
context:
space:
mode:
authorThomas Schwinge <thomas@schwinge.name>2010-08-13 13:26:06 +0200
committerThomas Schwinge <thomas@schwinge.name>2010-08-13 13:26:06 +0200
commitd27e0b0b2445c57e182a587d62987f86aae0c2af (patch)
tree88cd42b1eaa781c24e979023e2397653ad12e40d /open_issues/crashes_vs_system_load_cpu_load_rpc_load.mdwn
parent3c974df0e934c9e07aba1dcbb72969041fb41c81 (diff)
Another bunch of open issues.
Diffstat (limited to 'open_issues/crashes_vs_system_load_cpu_load_rpc_load.mdwn')
-rw-r--r--open_issues/crashes_vs_system_load_cpu_load_rpc_load.mdwn17
1 files changed, 17 insertions, 0 deletions
diff --git a/open_issues/crashes_vs_system_load_cpu_load_rpc_load.mdwn b/open_issues/crashes_vs_system_load_cpu_load_rpc_load.mdwn
new file mode 100644
index 00000000..4076d8d0
--- /dev/null
+++ b/open_issues/crashes_vs_system_load_cpu_load_rpc_load.mdwn
@@ -0,0 +1,17 @@
+[[!meta copyright="Copyright © 2010 Free Software Foundation, Inc."]]
+
+[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
+id="license" text="Permission is granted to copy, distribute and/or modify this
+document under the terms of the GNU Free Documentation License, Version 1.2 or
+any later version published by the Free Software Foundation; with no Invariant
+Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license
+is included in the section entitled [[GNU Free Documentation
+License|/fdl]]."]]"""]]
+
+IRC, unknown channel, unknown date:
+
+ <antrik> I have a theory
+ <antrik> when the system is under CPU load, the ext2 locking issues are more likely to happen
+ <antrik> I'm under the impression, that when doing something disk-intensive (like a compile job) *considerably* more often causes crashes, when doing *any* other activity in parallel -- be it other compile jobs, or CPU-only activities
+ <antrik> thinking about it, I'm not sure whether CPU-intensive is the decisive criterium, or maybe RPC-intensive...
+ <antrik> CPU load doesn't seem to have any effect -- neither alone, nor in combination with other testcases