| Summary: | sys-apps/portage-2.2.7 with dev-lang/python-2.7.5-r3:2.7 - strange performance problem | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Frank Krömmelbein <kroemmelbein> |
| Component: | Unclassified | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | antoni, floppym, nikoli, python |
| Priority: | Normal | ||
| Version: | 2.2 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: | https://bugs.gentoo.org/show_bug.cgi?id=498696 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | Enforce python_targets on pyxattr | ||
|
Description
Frank Krömmelbein
2014-01-18 17:06:30 UTC
That's the time it takes to resolve dependencies + the time needed to actually install the package? You should first separate the two. Add -p to get the dependency resolution time and then --nodeps to get the install time. Hello Sebastian, forget to memtion the problem occurs after the patching of the sources. Filesystem root Partition is ext4 on a fast Samsung 840 Pro SSD. Here are the times: time emerge -p gentoo-sources Python 2.7 real 0m6.849s user 0m6.706s sys 0m0.138s Python 3.3 real 0m6.265s user 0m6.184s sys 0m0.079s So nearly no time difference for dependency resolution. time emerge --nodeps gentoo-sources Python 2.7 real 7m33.432s user 1m39.035s sys 5m44.095s Python 3.3 real 1m13.797s user 1m1.688s sys 0m13.611s @python: Any idea why file system operations may be that much slower with 2.7 compared to 3.3? Frank Krömmelbein: Show: emerge -ptv dev-python/pyxattr (In reply to Arfrever Frehtes Taifersar Arahesis from comment #4) > Frank Krömmelbein: Show: > emerge -ptv dev-python/pyxattr Not installed! emerge -ptv dev-python/pyxattr These are the packages that would be merged, in reverse order: Calculating dependencies... done! [ebuild N ] dev-python/pyxattr-0.5.2 USE="{-test}" PYTHON_TARGETS="python2_7 python3_3 (-pypy2_0) -python2_6 -python3_2" 25 kB Total: 1 package (1 new), Size of downloads: 25 kB Should i install this? Python >=3.3 has xattr support in standard library. With older Python versions, Portage can use either dev-python/pyxattr (faster) or getfattr and setfattr from sys-apps/attr (slower). Anyway why would you want to use Portage with Python 2? (In reply to Arfrever Frehtes Taifersar Arahesis from comment #6) > Python >=3.3 has xattr support in standard library. > With older Python versions, Portage can use either dev-python/pyxattr > (faster) or getfattr and setfattr from sys-apps/attr (slower). > Thanks for the info! I just installed dev-python/pyxattr-0.5.2 and now with Python 2.7 time emerge --nodeps gentoo-sources real 1m14.420s user 1m1.902s sys 0m13.812s So nearly identical with Python 3.3. Wow! > Anyway why would you want to use Portage with Python 2? In the past i had some problems with Python 3.x, so i switched on my new installation also back to the trused Python 2.x Version. But i will try now Python 3.3. Thanks! Btw. Are there any known errors with dev-python/pyxattr? If not would it not make sense, to add a "xattr" useflag for python:2,7 which pulls in dev-python/pyxattr? I think i was not the only one who uses the older Python version, so this would be massiv speed improvement for this group. Created attachment 368112 [details, diff]
Enforce python_targets on pyxattr
This would resolve this issue for most python2 users; the exception being if they did not have python2_X in PYTHON_TARGETS but still invoke emerge with python2.X.
+ 20 Jan 2014; Mike Gilbert <floppym@gentoo.org> portage-2.2.8.ebuild, + portage-9999.ebuild: + Enforce python_targets on pyxattr dep, bug 498478. *** Bug 498696 has been marked as a duplicate of this bug. *** *** Bug 499488 has been marked as a duplicate of this bug. *** |
