You may have seen my thread "What keeps calling 'top' and 'grep' ?" since I'm trying to track down why Sage is making thousands of calls per second to top.
I then see this trac item http://sagetrac.org/sage_trac/ticket/6028 "get_memory_usage() sucks performance wise on Solaris" where mabshoff was suggesting using proc/$PID/psinfo instead of 'top'. He marked it 'blocker' but has since been changed to 'critical', but it is not fixed. Unfortunately, I can see no need to use 'top'. It it not even included in a standard distribution of Solaris. It is also well known to be inaccurate if used on modern Solaris versions. It we need some functionality in Sage, we should write code to do it, or make use of another tool. 'top' should not be used in this way. Unfortunately, Micheal's trac item give no clue where 'top' is being called, so I've no idea what package it is in. dave --~--~---------~--~----~------------~-------~--~----~ To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
