From bd0ffbcc4e0f7abf5e811850fb9ebd93ca649966 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Tue, 21 Dec 2010 19:10:42 +0100 Subject: Elaborate on DSLs, IDLs, code analysis, etc. --- open_issues/performance.mdwn | 19 +++++++++++++++---- 1 file changed, 15 insertions(+), 4 deletions(-) (limited to 'open_issues/performance.mdwn') diff --git a/open_issues/performance.mdwn b/open_issues/performance.mdwn index 3b4c4537..9b3701b3 100644 --- a/open_issues/performance.mdwn +++ b/open_issues/performance.mdwn @@ -8,10 +8,21 @@ 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]]."]]"""]] - * general [[RPC]] overhead +*Performance analysis* ([[!wikipedia Performance_analysis desc="Wikipedia +article"]]) deals with analyzing how computing resources are used for +completing a specified task. - * [[I/O System|io_system]] +[[Profiling]] is one relevant tool. - * [[fork]] +In [[microkernel]]-based systems, there is generally a considerable [[RPC]] +overhead. - * [[unit testing]] +In a multi-server system, it is non-trivial to implement a high-performance +[[I/O System|io_system]]. + +When providing [[faq/POSIX_compatibility]] (and similar interfaces) in an +environemnt that doesn't natively implement these interfaces, there may be a +severe performance degradation. For example, in this [[`fork` system +call|/glibc/fork]]'s case. + +[[Unit_testing]] can be used for tracking performance regressions. -- cgit v1.2.3