Dear all, my name is Thilo Reski and I'm with DB Systel, IT Service Provider for German Railways.
I am currently working on load tests on several PeopleSoft applications running in Solaris 10 zones. For controlling and monitoring I use Loadrunner (Mercury, HP). For unix resource monitoring, Loadrunner has a build-in interface to connect to rstatd demons on the monitored machines. When monitoring the machine resources of the test candidates with rstatd, I noticed that the rstatd monitor logs only information on the global zone, whatever zone it is connected to. Thus, with rstatd, there is no chance to achive resource usage information of local zones. Instead, all local zones running in the same global zone report the same cpu load, memory usage and io stats, when looking through the eyes of rstatd. Looking closer, I noticed that also tools like top do not distinguish perfect between zones. E.g. running top in a local zone shows the local process and their consumption of resources only, but cpu load is displayed just for the global zone :-( Thus, I came to DTrace. I found the brilliant DTrace-Toolkit and played around on a VM-Ware appliance with 3 global zones. (I have thee feeling, that this does not violate any licence ....) I found zvmstat, cputimes, cpudists and some more, which seem usefull. Unfortunately, I did not find a D-program which monitors memory usage or cpu load per zone. (I understand, that the memory and cpu is shared between the zones, which doesn't make it easier.) My goal is to log cpu load, cpu times, io, and memory consumption according to the zones during the tests. I want to know. e.g. what portion of the load, measurable in the global zone, comes from which of the local ones. My general idea to achieve this is to combine e.g. the D-programs zvmstat and cputimes to get the cpu times of processes in the local zones. One reason for this is, that I have no access to the configration in the test environment. I don't even know how many zones are configured and running, so the global zone resource usage is of little use. Now my questions: a) Does it comply to the licence of the DTrace-Toolkit, if I change the D-programs and run it to monitor load tests in a commercial environment? (I am no lawyer, but I have the feeling that I can do that.) b) If "yes" to a): Is the sketched idea of using DTrace reasonable? Or am I definetely wrong, e.g. zone oriented monitoring makes no sense at all or there are other tools available for this task? c) If "yes" to b): Is zone monitoring in the DTrace Toolkit available and I am just to dumb to find it - or is it elsewhere available? If "no" to c) I will proceed and post everything here. Bestest from Frankfurt, Germany This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
