First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 135488
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Andrew Ross (RETIRED) <aross@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: James Rowe <jnrowe@gmail.com>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
mercurial-module_optimise.patch mercurial-module_optimise.patch patch James Rowe 2006-06-04 02:46 0000 434 bytes Details | Diff
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 135488 depends on: Show dependency tree
Bug 135488 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2006-06-04 02:45 0000 
Currently the mercurial ebuild doesn't optimise the hgext python
directory, which can result in a severe slow down on startup if a user has
enabled any of the affected plugins.

  The attached patch fixes this by setting PYTHON_MODNAME, so the hgext dir
is considered too.

  It definitely isn't a scientific test but running "time for i in {0..100};
do hg help; done" yields a 75% speed up with the patch applied and the mq
extension enabled.  It makes a significant difference on my baby epia box,
but obviously much less on faster boxes.

------- Comment #1 From James Rowe 2006-06-04 02:46:44 0000 ------- 
Created an attachment (id=88328) [edit]
mercurial-module_optimise.patch

------- Comment #2 From Andrew Ross (RETIRED) 2006-08-23 18:52:19 0000 ------- 
Fixed in dev-util/mercurial-0.9.1-r1 - thanks for your contribution.
First Last Prev Next    No search results available      Search page      Enter new bug