#6028: get_memory_usage() sucks performance wise on Solaris
------------------------+---------------------------------------------------
Reporter: mabshoff | Owner: mabshoff
Type: defect | Status: new
Priority: critical | Milestone: sage-4.3.4
Component: solaris | Keywords:
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
------------------------+---------------------------------------------------
Comment(by drkirkby):
I do not know what hardware Micheal used when he found the CPU time used
was about a second, but on a dual processor 900 MHz Sun Blade 2000, with a
load average of 1.0, the times are '''much''' faster using 'prstat'. This
is a slightly modified version of Sage 4.3.3, so it builds on Solaris.
Since the load average was 1.0, and its dual processor, I doubt it would
be any faster on an idle system.
The CPU time can't be measured (displayed as 0.00 s), but the wall time is
0.08s.
{{{
Exiting SAGE (CPU time 0m0.20s, Wall time 5m59.86s).
drkir...@redstart:~/fresh/sage-4.3.3$ ./sage
----------------------------------------------------------------------
| Sage Version 4.3.3, Release Date: 2010-02-21 |
| Type notebook() for the GUI, and license() for information. |
----------------------------------------------------------------------
sage: time get_memory_usage()
CPU times: user 0.00 s, sys: 0.00 s, total: 0.00 s
Wall time: 0.08 s
91.0
}}}
This means using 'prstat' to get the times is '''much faster''' than using
'top'.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/6028#comment:5>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
