Re: some performance problems with async console client

2002-06-14 Thread Roland McGrath
> On Fri, Jun 14, 2002 at 05:01:02PM -0400, Roland McGrath wrote: > > > > (well, ports_manage_multithreaded is still necessary, as Mach > > > > doesn't let you receive messages in the order they were sent easily) > > > > I'm not sure what Marcus means here. Messages are dequeued from a > > parti

Re: some performance problems with async console client

2002-06-14 Thread Marcus Brinkmann
On Fri, Jun 14, 2002 at 05:01:02PM -0400, Roland McGrath wrote: > > > (well, ports_manage_multithreaded is still necessary, as Mach > > > doesn't let you receive messages in the order they were sent easily) > > I'm not sure what Marcus means here. Messages are dequeued from a > particular port i

Re: some performance problems with async console client

2002-06-14 Thread Roland McGrath
> > (well, ports_manage_multithreaded is still necessary, as Mach > > doesn't let you receive messages in the order they were sent easily) I'm not sure what Marcus means here. Messages are dequeued from a particular port in the order they were sent (if sending was serialized). You can receive on

Re: some performance problems with async console client

2002-06-14 Thread Niels Möller
Marcus Brinkmann <[EMAIL PROTECTED]> writes: > (well, ports_manage_multithreaded is still necessary, as Mach > doesn't let you receive messages in the order they were sent easily) Huh, that sounds hairy and suboptimal. For instance, I'd expect that if a thread of mine sends some asyncronous and

Re: some performance problems with async console client

2002-06-14 Thread Marcus Brinkmann
On Fri, Jun 14, 2002 at 10:10:05PM +0200, Niels Möller wrote: > One way to organize the client may be as follows: I pondered this today, and came to an almost identical model! I am happy to get this second opinion. > Second step: Let the notification thread check the length of the > queue, if

Re: some performance problems with async console client

2002-06-14 Thread Niels Möller
Marcus Brinkmann <[EMAIL PROTECTED]> writes: > Another way to improve the situation is to make reception > of update notifications and the actual screen updates asynchronous in > the client, too. This requires a bit more logic, but adds flexibility > in that the client can notice if a lot of out

some performance problems with async console client

2002-06-14 Thread Marcus Brinkmann
Hi, I just added the seqno serialization in the console client, and noticed that there is a severe performance problem. The issue is that the console server is rocking fast, and the client can not keep up with this speed in updating the display. Take a "find /share > term" command. It will write