#6208: [with patch, needs review] Improving gap interface by pre-compiling 
certain
regular expressions
-------------------------+--------------------------------------------------
 Reporter:  SimonKing    |       Owner:  SimonKing                              
     Type:  enhancement  |      Status:  new                                    
 Priority:  major        |   Milestone:  sage-4.0.2                             
Component:  interfaces   |    Keywords:  gap interface expect regular expression
-------------------------+--------------------------------------------------

Comment(by SimonKing):

 Concerning the timings, one cautious remark:

 I ''did'' have the good timing with my patch. But later, I tried again,
 and it was not as good (though still faster than without the patch).
 {{{
 ----------------------------------------------------------------------
 | Sage Version 4.0, Release Date: 2009-05-29                         |
 | Type notebook() for the GUI, and license() for information.        |
 ----------------------------------------------------------------------
 Loading Sage library. Current Mercurial branch is: expect-devel
 sage: G=SymmetricGroup(7)
 sage: time L=[X for X in G if X.order()==2]
 CPU times: user 8.50 s, sys: 1.88 s, total: 10.39 s
 Wall time: 13.05 s
 }}}

 Perhaps someone can explain why this happens. It seems that this is a bad
 benchmark test.

 So, I would appreciate a better (more stable) example.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/6208#comment:1>
Sage <http://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
-~----------~----~----~----~------~----~------~--~---

Reply via email to