Process monitor: the next generation
Locked
 
|
Hello!
We are currently working on a new process browser (codename: Loom). You have probably noticed that the Process Browser is not exactly the tool you want to use to understand how processes behave. The process browser may be one of the oldest piece of code that has not been touched for a long long time. We are going toward something that looks like the Activity Monitor (e.g., [*]), useful to find out which programs is heating up your laptop. We will have nice curves that shows you the CPU consumption. Something that the process browser has never been able to do so far. We have a lot of ideas, but we still think it is a good idea to get your inputs guys. What are the features you would like to see in a super cool process browser? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Re: Process monitor: the next generation
|
|
Alexandre
Sometimes I change the sample time to a very short time and then observe how Waiting Context changes. This gives me an idea as to what processes are busy and a little about what they are doing. It would be nice if there were a cleaner mechanism for seeing what a process is doing without halting it. One other point of caution; the process monitor is also used to assist in recovering a runaway system. You don't want the process assessment activity to impede this ability. Terry =========================================================== Terry Raymond Crafted Smalltalk 80 Lazywood Ln. Tiverton, RI 02878 (401) 624-4517 [hidden email] =========================================================== > -----Original Message----- > From: [hidden email] [mailto:[hidden email]] On > Behalf Of Alexandre Bergel > Sent: Thursday, September 06, 2012 10:26 AM > To: VisualWorks mailing list list > Subject: [vwnc] Process monitor: the next generation > > Hello! > > We are currently working on a new process browser (codename: Loom). You > have probably noticed that the Process Browser is not exactly the tool you > want to use to understand how processes behave. The process browser may > be one of the oldest piece of code that has not been touched for a long > time. > > We are going toward something that looks like the Activity Monitor (e.g., > [*]), useful to find out which programs is heating up your laptop. We will > have nice curves that shows you the CPU consumption. Something that the > process browser has never been able to do so far. > > We have a lot of ideas, but we still think it is a good idea to get your inputs > guys. > What are the features you would like to see in a super cool process browser? > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Re: Process monitor: the next generation
|
|
In reply to this post by abergel
Alexandre,
It would be nice to have emphasis on processes that are a #windowProcess referenced by a WindowManager.baseProcess. Those are the processes that freeze the windows when blocked and also the processes that applications run in most. Perhaps something like this: Process>>isWindowProcess " Process allInstances groupedBy: [:ea | ea isWindowProcess ]. " | nilOrWm | ^(nilOrWm := self environmentAt: #WindowManager) notNil and: [self == nilOrWm windowProcess] It would be useful to see processes grouped by window manager. Too often there are over-informative printOn: implementations that cause infinite loops just by putting a breakpoint in something. It would be nice if something could interrupt loops like these before the crash. VA avoids these problems by having #debugPrintOn: separate from #printOn: so debuggers and stack dumpers can catch and avoid problems. If VW won't avoid problems like these then hopefully the new Process Browser will be able to recover from the situation. To interrupt at that level you'd probably need to tweak ProcessorScheduler or the VM. The "Waiting Context" column is the only indication of what a process is paused for. It would be nice if the waiting context had the ability to tell details about the wait. If waiting on a semaphore then the semaphore could show things like signal counts and waiting processes. If waiting on a delay then the delay could show delayDuration and ms until resumptionTime. If waiting for an EventQueue then the queue then it might be useful to show queue contents size (unguarded) and sempahore signal counts. This should be implemented so that information can be customized by application code (for example: 'receiver debugPrintOn: aStream waitingAt: selector'). It might be useful if the process had some efficient form of note of when it was last made active. If you had that then the Process Browser would have a way to show how long processes are inactive due to scheduling. Scheduling issues are common when people try to use background processes. This would be a clue to a developer for why work in a forked process wasn't really any faster (because did didn't even get scheduled until after the forking process waited and (sometimes) other processes did their work). Paul Baumann -----Original Message----- From: [hidden email] [mailto:[hidden email]] On Behalf Of Alexandre Bergel Sent: Thursday, September 06, 2012 10:26 To: VisualWorks mailing list list Subject: [vwnc] Process monitor: the next generation Hello! We are currently working on a new process browser (codename: Loom). You have probably noticed that the Process Browser is not exactly the tool you want to use to understand how processes behave. The process browser may be one of the oldest piece of code that has not been touched for a long long time. We are going toward something that looks like the Activity Monitor (e.g., [*]), useful to find out which programs is heating up your laptop. We will have nice curves that shows you the CPU consumption. Something that the process browser has never been able to do so far. We have a lot of ideas, but we still think it is a good idea to get your inputs guys. What are the features you would like to see in a super cool process browser? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc This message may contain confidential information and is intended for specific recipients unless explicitly noted otherwise. If you have reason to believe you are not an intended recipient of this message, please delete it and notify the sender. This message may not represent the opinion of IntercontinentalExchange, Inc. (ICE), its subsidiaries or affiliates, and does not constitute a contract or guarantee. Unencrypted electronic mail is not secure and the recipient of this message is expected to provide safeguards from viruses and pursue alternate means of communication where privacy or a binding message is desired. _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Re: Process monitor: the next generation
|
|
In reply to this post by abergel
How will you be licensing Loom?
Cheers, Michael On 07/09/2012, at 12:25 AM, Alexandre Bergel <[hidden email]> wrote: > Hello! > > We are currently working on a new process browser (codename: Loom). You have probably noticed that the Process Browser is not exactly the tool you want to use to understand how processes behave. The process browser may be one of the oldest piece of code that has not been touched for a long long time. > > We are going toward something that looks like the Activity Monitor (e.g., [*]), useful to find out which programs is heating up your laptop. We will have nice curves that shows you the CPU consumption. Something that the process browser has never been able to do so far. > > We have a lot of ideas, but we still think it is a good idea to get your inputs guys. > What are the features you would like to see in a super cool process browser? > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
|
|
In reply to this post by Terry Raymond
> Sometimes I change the sample time to a very short time and then observe
> how Waiting Context changes. This gives me an idea as to what processes are > busy and a little about what they are doing. > It would be nice if there were a cleaner mechanism for seeing what a process > is doing > without halting it. We are working on estimating the amount of CPU consumption for each thread. As you said, understanding what a particular thread is doing would indeed be nice to have. A simple trace mechanism would be quite helpful. > One other point of caution; the process monitor is also used to assist in > recovering > a runaway system. You don't want the process assessment activity to impede > this ability. This is a difficult compromising point. Probably our profiler will not replace the process monitor. Process monitor is quite simple and has a low overhead. Loom is likely to have a greater footprint since it tells more about what's going on. The key point here is to offer the options to the programmer to choose the right balance. This will be the real value of Loom. We are aware of this and we will be careful. Cheers, Alexandre > > >> -----Original Message----- >> From: [hidden email] [mailto:[hidden email]] On >> Behalf Of Alexandre Bergel >> Sent: Thursday, September 06, 2012 10:26 AM >> To: VisualWorks mailing list list >> Subject: [vwnc] Process monitor: the next generation >> >> Hello! >> >> We are currently working on a new process browser (codename: Loom). You >> have probably noticed that the Process Browser is not exactly the tool you >> want to use to understand how processes behave. The process browser may >> be one of the oldest piece of code that has not been touched for a long > long >> time. >> >> We are going toward something that looks like the Activity Monitor (e.g., >> [*]), useful to find out which programs is heating up your laptop. We will >> have nice curves that shows you the CPU consumption. Something that the >> process browser has never been able to do so far. >> >> We have a lot of ideas, but we still think it is a good idea to get your > inputs >> guys. >> What are the features you would like to see in a super cool process > browser? >> >> Cheers, >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> _______________________________________________ >> vwnc mailing list >> [hidden email] >> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > > > > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
|
|
In reply to this post by Michael Lucas-Smith-2
> How will you be licensing Loom?
It will probably be MIT. Naturally, particular customization will be possible. Thanks to some generous sponsors, we have been able to live and keep our fun by delivering MIT products. Loom will probably follow the same path than Kai, Hapao and Roassal. Cheers, Alexandre > > On 07/09/2012, at 12:25 AM, Alexandre Bergel <[hidden email]> wrote: > >> Hello! >> >> We are currently working on a new process browser (codename: Loom). You have probably noticed that the Process Browser is not exactly the tool you want to use to understand how processes behave. The process browser may be one of the oldest piece of code that has not been touched for a long long time. >> >> We are going toward something that looks like the Activity Monitor (e.g., [*]), useful to find out which programs is heating up your laptop. We will have nice curves that shows you the CPU consumption. Something that the process browser has never been able to do so far. >> >> We have a lot of ideas, but we still think it is a good idea to get your inputs guys. >> What are the features you would like to see in a super cool process browser? >> >> Cheers, >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> _______________________________________________ >> vwnc mailing list >> [hidden email] >> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
|
|
In reply to this post by Paul Baumann
Excellent feedback Paul.
We will keep you informed about our progresses Thanks, Alexandre On Sep 6, 2012, at 3:42 PM, Paul Baumann <[hidden email]> wrote: > Alexandre, > > It would be nice to have emphasis on processes that are a #windowProcess referenced by a WindowManager.baseProcess. Those are the processes that freeze the windows when blocked and also the processes that applications run in most. Perhaps something like this: > > Process>>isWindowProcess > " Process allInstances groupedBy: [:ea | ea isWindowProcess ]. " > > | nilOrWm | > ^(nilOrWm := self environmentAt: #WindowManager) notNil > and: [self == nilOrWm windowProcess] > > It would be useful to see processes grouped by window manager. > > Too often there are over-informative printOn: implementations that cause infinite loops just by putting a breakpoint in something. It would be nice if something could interrupt loops like these before the crash. VA avoids these problems by having #debugPrintOn: separate from #printOn: so debuggers and stack dumpers can catch and avoid problems. If VW won't avoid problems like these then hopefully the new Process Browser will be able to recover from the situation. To interrupt at that level you'd probably need to tweak ProcessorScheduler or the VM. > > The "Waiting Context" column is the only indication of what a process is paused for. It would be nice if the waiting context had the ability to tell details about the wait. If waiting on a semaphore then the semaphore could show things like signal counts and waiting processes. If waiting on a delay then the delay could show delayDuration and ms until resumptionTime. If waiting for an EventQueue then the queue then it might be useful to show queue contents size (unguarded) and sempahore signal counts. This should be implemented so that information can be customized by application code (for example: 'receiver debugPrintOn: aStream waitingAt: selector'). > > It might be useful if the process had some efficient form of note of when it was last made active. If you had that then the Process Browser would have a way to show how long processes are inactive due to scheduling. Scheduling issues are common when people try to use background processes. This would be a clue to a developer for why work in a forked process wasn't really any faster (because did didn't even get scheduled until after the forking process waited and (sometimes) other processes did their work). > > Paul Baumann > > > > -----Original Message----- > From: [hidden email] [mailto:[hidden email]] On Behalf Of Alexandre Bergel > Sent: Thursday, September 06, 2012 10:26 > To: VisualWorks mailing list list > Subject: [vwnc] Process monitor: the next generation > > Hello! > > We are currently working on a new process browser (codename: Loom). You have probably noticed that the Process Browser is not exactly the tool you want to use to understand how processes behave. The process browser may be one of the oldest piece of code that has not been touched for a long long time. > > We are going toward something that looks like the Activity Monitor (e.g., [*]), useful to find out which programs is heating up your laptop. We will have nice curves that shows you the CPU consumption. Something that the process browser has never been able to do so far. > > We have a lot of ideas, but we still think it is a good idea to get your inputs guys. > What are the features you would like to see in a super cool process browser? > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > > > This message may contain confidential information and is intended for specific recipients unless explicitly noted otherwise. If you have reason to believe you are not an intended recipient of this message, please delete it and notify the sender. This message may not represent the opinion of IntercontinentalExchange, Inc. (ICE), its subsidiaries or affiliates, and does not constitute a contract or guarantee. Unencrypted electronic mail is not secure and the recipient of this message is expected to provide safeguards from viruses and pursue alternate means of communication where privacy or a binding message is desired. > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Re: Process monitor: the next generation
|
|
In reply to this post by abergel
#1
Some kind of coarse-grained timing diagram would be neat. Processes = Y axis, time = X axis, configurable timespan (e.g. 100ms). Show a bar if the process has been active withing the timespan. Maybe use color to display the amount of activity. #2 The "waiting context" shown by the current ProcessMonitor is not very helpful, it usually shows Semaphore>>waitIfCurtailedSignal, Delay>>wait etc. So either showing a bit more context or skipping the ubiquitous parts at the top of context could help understanding more quickly what the process is currently doing.
|
Re: Process monitor: the next generation
|
|
In reply to this post by abergel
>> A simple trace mechanism would be quite helpful.
How would that differ from what "View Stack", "Dump Stack...", and "Debug" menu options already do for a selected process? I suspect what you mean is to have integration with time or allocation profiling tools. I'm thinking that you'd right click on a process and select a profiling tool from a menu. An "End Profiling" button would be enabled while profiling is going on. You usually only want one profiling tool running at a time. Pressing the button would end whatever profiling is going on and open the profiling results window. The profiler would probably be of the Multi*Profiler variety that can monitor more than one process. The profiler could collect and/or display results for the processes that were selected for profiling. Having a general "End Profiling" would also be useful for when the Multi*Profiler is started but never stopped. Paul Baumann -----Original Message----- From: [hidden email] [mailto:[hidden email]] On Behalf Of Alexandre Bergel Sent: Friday, September 07, 2012 09:57 To: Terry Raymond Cc: 'VisualWorks mailing list list' Subject: Re: [vwnc] Process monitor: the next generation > Sometimes I change the sample time to a very short time and then observe > how Waiting Context changes. This gives me an idea as to what processes are > busy and a little about what they are doing. > It would be nice if there were a cleaner mechanism for seeing what a process > is doing > without halting it. We are working on estimating the amount of CPU consumption for each thread. As you said, understanding what a particular thread is doing would indeed be nice to have. A simple trace mechanism would be quite helpful. > One other point of caution; the process monitor is also used to assist in > recovering > a runaway system. You don't want the process assessment activity to impede > this ability. This is a difficult compromising point. Probably our profiler will not replace the process monitor. Process monitor is quite simple and has a low overhead. Loom is likely to have a greater footprint since it tells more about what's going on. The key point here is to offer the options to the programmer to choose the right balance. This will be the real value of Loom. We are aware of this and we will be careful. Cheers, Alexandre > > >> -----Original Message----- >> From: [hidden email] [mailto:[hidden email]] On >> Behalf Of Alexandre Bergel >> Sent: Thursday, September 06, 2012 10:26 AM >> To: VisualWorks mailing list list >> Subject: [vwnc] Process monitor: the next generation >> >> Hello! >> >> We are currently working on a new process browser (codename: Loom). You >> have probably noticed that the Process Browser is not exactly the tool you >> want to use to understand how processes behave. The process browser may >> be one of the oldest piece of code that has not been touched for a long > long >> time. >> >> We are going toward something that looks like the Activity Monitor (e.g., >> [*]), useful to find out which programs is heating up your laptop. We will >> have nice curves that shows you the CPU consumption. Something that the >> process browser has never been able to do so far. >> >> We have a lot of ideas, but we still think it is a good idea to get your > inputs >> guys. >> What are the features you would like to see in a super cool process > browser? >> >> Cheers, >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> _______________________________________________ >> vwnc mailing list >> [hidden email] >> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > > > > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc This message may contain confidential information and is intended for specific recipients unless explicitly noted otherwise. If you have reason to believe you are not an intended recipient of this message, please delete it and notify the sender. This message may not represent the opinion of IntercontinentalExchange, Inc. (ICE), its subsidiaries or affiliates, and does not constitute a contract or guarantee. Unencrypted electronic mail is not secure and the recipient of this message is expected to provide safeguards from viruses and pursue alternate means of communication where privacy or a binding message is desired. _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Re: Process monitor: the next generation
|
|
In reply to this post by Terry Raymond
I second Terry's comment. If you're running out of memory, the process
monitor is supposed to help you figure stuff out. If the process monitor itself runs out of memory while handling a memory emergency, then the VM will stop your image. You may want to determine whether to simply replace the process monitor or provide a separate activity monitor that serves different purposes. On 9/6/12 8:50 , Terry Raymond wrote: > Alexandre > > Sometimes I change the sample time to a very short time and then observe > how Waiting Context changes. This gives me an idea as to what processes are > busy and a little about what they are doing. > It would be nice if there were a cleaner mechanism for seeing what a process > is doing > without halting it. > > One other point of caution; the process monitor is also used to assist in > recovering > a runaway system. You don't want the process assessment activity to impede > this ability. > > Terry > > =========================================================== > Terry Raymond > Crafted Smalltalk > 80 Lazywood Ln. > Tiverton, RI 02878 > (401) 624-4517 [hidden email] > =========================================================== > >> -----Original Message----- >> From: [hidden email] [mailto:[hidden email]] On >> Behalf Of Alexandre Bergel >> Sent: Thursday, September 06, 2012 10:26 AM >> To: VisualWorks mailing list list >> Subject: [vwnc] Process monitor: the next generation >> >> Hello! >> >> We are currently working on a new process browser (codename: Loom). You >> have probably noticed that the Process Browser is not exactly the tool you >> want to use to understand how processes behave. The process browser may >> be one of the oldest piece of code that has not been touched for a long > long >> time. >> >> We are going toward something that looks like the Activity Monitor (e.g., >> [*]), useful to find out which programs is heating up your laptop. We will >> have nice curves that shows you the CPU consumption. Something that the >> process browser has never been able to do so far. >> >> We have a lot of ideas, but we still think it is a good idea to get your > inputs >> guys. >> What are the features you would like to see in a super cool process > browser? >> >> Cheers, >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> _______________________________________________ >> vwnc mailing list >> [hidden email] >> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > > > > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > . > vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Re: Process monitor: the next generation
|
|
In reply to this post by abergel
> This is a difficult compromising point. Probably our profiler will not replace the process monitor. Process monitor is quite simple and has a low overhead.
> Loom is likely to have a greater footprint since it tells more about what's going on. The key point here is to offer the options to the programmer to choose the right balance. This will be the real value of Loom. > We are aware of this and we will be careful. Yes, that's right. Also, be careful when tracing through system processes... if, for example, the tracing depends on the timer system, then tracing the timer process may or may not be a good idea. I don't know myself right now, of course, since I do not know what you have in mind or how the code looks like. This is just a comment :). Andres. _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
|
|
In reply to this post by Andres Valloud-4
Thanks for all your advices...
Hopefully soon there will be something to try out Cheers, Alexandre On Sep 11, 2012, at 11:24 PM, Andres Valloud <[hidden email]> wrote: > I second Terry's comment. If you're running out of memory, the process monitor is supposed to help you figure stuff out. If the process monitor itself runs out of memory while handling a memory emergency, then the VM will stop your image. You may want to determine whether to simply replace the process monitor or provide a separate activity monitor that serves different purposes. > > On 9/6/12 8:50 , Terry Raymond wrote: >> Alexandre >> >> Sometimes I change the sample time to a very short time and then observe >> how Waiting Context changes. This gives me an idea as to what processes are >> busy and a little about what they are doing. >> It would be nice if there were a cleaner mechanism for seeing what a process >> is doing >> without halting it. >> >> One other point of caution; the process monitor is also used to assist in >> recovering >> a runaway system. You don't want the process assessment activity to impede >> this ability. >> >> Terry >> >> =========================================================== >> Terry Raymond >> Crafted Smalltalk >> 80 Lazywood Ln. >> Tiverton, RI 02878 >> (401) 624-4517 [hidden email] >> =========================================================== >> >>> -----Original Message----- >>> From: [hidden email] [mailto:[hidden email]] On >>> Behalf Of Alexandre Bergel >>> Sent: Thursday, September 06, 2012 10:26 AM >>> To: VisualWorks mailing list list >>> Subject: [vwnc] Process monitor: the next generation >>> >>> Hello! >>> >>> We are currently working on a new process browser (codename: Loom). You >>> have probably noticed that the Process Browser is not exactly the tool you >>> want to use to understand how processes behave. The process browser may >>> be one of the oldest piece of code that has not been touched for a long >> long >>> time. >>> >>> We are going toward something that looks like the Activity Monitor (e.g., >>> [*]), useful to find out which programs is heating up your laptop. We will >>> have nice curves that shows you the CPU consumption. Something that the >>> process browser has never been able to do so far. >>> >>> We have a lot of ideas, but we still think it is a good idea to get your >> inputs >>> guys. >>> What are the features you would like to see in a super cool process >> browser? >>> >>> Cheers, >>> Alexandre >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> _______________________________________________ >>> vwnc mailing list >>> [hidden email] >>> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc >> >> >> >> _______________________________________________ >> vwnc mailing list >> [hidden email] >> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc >> . >> > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
«
Return to VisualWorks
|
1 view|%1 views
| Free forum by Nabble | Edit this page |