Run oprofile and see where this mod is spending its time. strace is also an option to see what API it's using (select with a timeout probably).
BTW (not related to your problem) I have submitted a set of fixes to the mono folks that will make a huge set of methods available that currently aren't. (The s390x port had only been using a simplistic vtable lookup whereas the other platforms moved to "IMT" - a method trampolining scheme. A lot of the new APIs require this mechanism.) On 8/17/10 9:03 AM, "Mike Friesenegger" <[email protected]> wrote: Hello Berry, I do not know the answer to your question but I know some that might. Let me run this by them and get back to you. Mike >>> "van Sleeuwen, Berry" 08/17/10 6:58 AM >>> Hi listers, We have configured a SLES11 SP1 with apache and mono. When we start the httpd the server is active all the time, keeping it in Q3 all the time. We have determined that indeed the mono module is the cause for the wakeup of the guest. Powertop shows that 50%-65% of the time mono was responsible for wakeup-from-idle and when we remove mono the guest drops from queue. We have been looking at some options at this time. First we have changed KeepAlive too Off in server-tuning.conf, but no luck. Next we have created a new configuration for mono in the /etc/apache2/conf.d directory to replace the default mod_mono.conf. # note, this config has been created using an online tool to create configfiles... we added LoadModule and MONO_MANAGED_WATCHER. LoadModule mono_module /usr/lib64/apache2/mod_mono.so Alias /sds "/srv/www/htdocs/sds" MonoServerPath sds "/usr/bin/mod-mono-server2" MonoSetEnv sds MONO_IOMAP=all;MONO_MANAGED_WATCHER=disable MonoApplications sds "/sds:/srv/www/htdocs/sds" Allow from all Order allow,deny MonoSetServerAlias sds SetHandler mono SetOutputFilter DEFLATE SetEnvIfNoCase Request_URI "\.(?:gif|jpe?g|png)$" no-gzip dont-vary AddOutputFilterByType DEFLATE text/html text/plain text/xml text/javascript I had found a reference for the MONO_MANAGED_WATCHER that should be set to disable to prevent mono from watching (polling) for filesystem updates. But this also has no effect, though I don't know for sure if this config is really what it should be. But all this did not yet give us a guest that drops out of queue, it still remains in Q3. Any ideas what can we do to reduce the activity of this guest? Met vriendelijke groet/With kind regards, Berry van Sleeuwen Flight Forum 3000 5657 EW Eindhoven ( +31 (0)6 22564276 Atos Origin MO CF SC Mainframe Services ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/ ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/ ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
