From 0447d6f115c94f5815189d1be4211991ef665d9e Mon Sep 17 00:00:00 2001 From: "https://me.yahoo.com/a/g3Ccalpj0NhN566pHbUl6i9QF0QEkrhlfPM-#b1c14" Date: Mon, 16 Feb 2015 20:08:52 +0100 Subject: update for rename of open_issues/profiling.mdwn to service_solahart_jakarta_selatan__082122541663/profiling.mdwn --- community/gsoc/project_ideas/dtrace.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'community/gsoc') diff --git a/community/gsoc/project_ideas/dtrace.mdwn b/community/gsoc/project_ideas/dtrace.mdwn index 6261c03e..1bc343f5 100644 --- a/community/gsoc/project_ideas/dtrace.mdwn +++ b/community/gsoc/project_ideas/dtrace.mdwn @@ -19,7 +19,7 @@ problems, these are mostly just guesses. Better understanding what really causes bad performance is necessary to improve the situation. For that, we need tools for performance measurements. While all kinds of more -or less specific [[open_issues/profiling]] tools could be conceived, the most promising and +or less specific [[service_solahart_jakarta_selatan__082122541663/profiling]] tools could be conceived, the most promising and generic approach seems to be a framework for logging certain events in the running system (both in the microkernel and in the Hurd servers). This would allow checking how much time is spent in certain modules, how often certain -- cgit v1.2.3