From mint-bounce@lists.fishpool.fi Tue Aug 24 06:46:06 2010 To: mint Subject: Re: [MiNT] AES related question: How to keep track if my application MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Date: Tue, 24 Aug 2010 12:44:24 +0200 From: m0n0 Reply-To: ole@monochrom.net In-Reply-To: <569388.163599314-sendEmail@descaro> References: <569388.163599314-sendEmail@descaro> Message-ID: <7dbb5e254d781a3afda8d46ce220f8a5-EhVcX1lFRQVaRwYcDTpQCEFddQZLVF5dQUNBAjBTXF5bVkYLV0FzCTpUX1ddR0EEWVxd-webmailer2@server08.webmailer.hosteurope.de> X-Sender: ole@monochrom.net User-Agent: Host Europe Webmailer/2.0 X-HE-Access: Yes X-bounce-key: webpack.hosteurope.de;ole@monochrom.net;1282646664;d058e47d; X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: ole@monochrom.net Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Am Dienstag, den 24.08.2010, 12:03 +0200 schrieb "Helmut Karlowski" : >> Sorry, that seems wrong to me - I should call EvntMulti with longer >> timeouts to give more CPU time to the Rendering/Network code? That's not > > That's what I thought. That's maybe true for an mult-threaded environment...? > When it works it's ok, just find the best compromise between overhead > and response-time. > BTW: I don't think evnt_multi alone consumes much > CPU, to me it's like a second-layer-scheduler with refined > application-control. But I hope you use the improved version with the > pointer instead of 33 parameters on stack? I'm using the WinDom version, haven't looked in the internals. Greets, m