Re: [gentoo-user] Re: Now Know Why Portage Is So Slow
Hemmann, Volker Armin wrote: On Friday 26 May 2006 21:28, Alexander Skwar wrote: Hemmann, Volker Armin wrote: On Friday 26 May 2006 18:13, Bo Ørsted Andresen wrote: Friday 26 May 2006 17:51 skrev Hemmann, Volker Armin: ok, but still less to type ;) But esearch is more than twice as long as eix... ;) I am using search less, than syncing, so still a win, and it is only eseatab ;) Which is still 5 characters compared to 3 characters for eix :) but eix-sync is still longer than esync (8 to 5) ;) Nah, it's 5 to 5, so eix-sync is NOT longer than esync... eix-tab So, at best, eix is as bad as esearch, but normally eix is faster to use - in every aspect. Alexander Skwar -- May your future be limited only by your dreams. -- Christa McAuliffe -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: Now Know Why Portage Is So Slow
On Sat, 27 May 2006 08:16:02 +0200, Alexander Skwar wrote: but eix-sync is still longer than esync (8 to 5) ;) Nah, it's 5 to 5, so eix-sync is NOT longer than esync... I really think you guys should read this page :) http://www.gentoo.org/doc/en/cron-guide.xml -- Neil Bothwick Everything's back to normal. Damn. signature.asc Description: PGP signature
Re: [gentoo-user] Re: Now Know Why Portage Is So Slow
On Sat, 27 May 2006, Neil Bothwick wrote: On Sat, 27 May 2006 08:16:02 +0200, Alexander Skwar wrote: but eix-sync is still longer than esync (8 to 5) ;) Nah, it's 5 to 5, so eix-sync is NOT longer than esync... I really think you guys should read this page :) http://www.gentoo.org/doc/en/cron-guide.xml Long story short, sudo echo emerge --sync 1/dev/null 21 /etc/cron.daily/portsync, sudo chmod 755 /etc/cron.daily/portsync Assuming you're on vixie-cron at least. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: Now Know Why Portage Is So Slow
Steven Susbauer wrote: Long story short, sudo echo emerge --sync 1/dev/null 21 /etc/cron.daily/portsync, sudo chmod 755 /etc/cron.daily/portsync How will this update either the eix or the esearch databases? Alexander Skwar -- I haven't been married in over six years, but we had sexual counseling every day from Oral Roberts!! -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: Now Know Why Portage Is So Slow
On Fri, 2006-05-26 at 08:25 +0100, Neil Bothwick wrote: Also, unless this have changed dramatically, eix's database update is *much* faster than that of esearch - seconds vs. minutes. I've heard that argument before, and I don't know why some people see that behaviour - esearch only takes seconds for me... -- Iain Buchanan iaindb at netspace dot net dot au You should avoid hedging, at least that's what I think. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: Now Know Why Portage Is So Slow
Iain Buchanan wrote: On Fri, 2006-05-26 at 08:25 +0100, Neil Bothwick wrote: Also, unless this have changed dramatically, eix's database update is *much* faster than that of esearch - seconds vs. minutes. I've heard that argument before, and I don't know why some people see that behaviour - esearch only takes seconds for me... Are you really talking about *esearch* or about eupdate (or what's it called)? *esearch* is fast for me as well - but the update was so slow, that I now finally dumped it. Alexander Skwar -- You have all eternity to be cautious in when you're dead. -- Lois Platford -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: Now Know Why Portage Is So Slow
Saturday 27 May 2006 13:42 skrev Iain Buchanan: I've heard that argument before, and I don't know why some people see that behaviour - esearch only takes seconds for me... It's not the esearch binary versus the eix binary where there is a big difference. It's eupdatedb which takes a very long time compared to update-eix. -- Bo Andresen pgpaMAa6kICi2.pgp Description: PGP signature
Re: [gentoo-user] Re: Now Know Why Portage Is So Slow
On 5/27/06, Bo Ørsted Andresen [EMAIL PROTECTED] wrote: Saturday 27 May 2006 13:42 skrev Iain Buchanan: I've heard that argument before, and I don't know why some people see that behaviour - esearch only takes seconds for me... It's not the esearch binary versus the eix binary where there is a big difference. It's eupdatedb which takes a very long time compared to update-eix. Is this getting to the point of ferocity of the legendary emacs vs. vi wars I've heard so much about? At this rate, I'm inclined to recommend Kuroo to all of you. I've been kicking the tires in on it, and it's really quite good. http://kuroo.org/ app-portage/kuroo -- == GCv3.12 == GCS d-(++) s+: a? C++ UL+ P+ L++ E--- W+(+++) N++ o? K? w--- O? M+ V? PS- PE+ Y-(--) PGP- t+++ 5? X R tv-- b+ DI+++ D+ G e* h- !r !y = END GCv3.12 -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: Now Know Why Portage Is So Slow
On Fri, 26 May 2006 07:48:30 +0200, Alexander Skwar wrote: Has the additional advantage, that it lists all new and updates packages, when the sync is finished. You don't know eix, do you? Because, what you list here as an advantage is no advantage, as eix does the same. Also, unless this have changed dramatically, eix's database update is *much* faster than that of esearch - seconds vs. minutes. -- Neil Bothwick ... Never say anything more predictive than Watch this! signature.asc Description: PGP signature
Re: [gentoo-user] Re: Now Know Why Portage Is So Slow
On Fri, 26 May 2006 09:21:42 +0930, Iain Buchanan wrote: I didn't even have to edit /boot/grub/menu.lst! Are you sure you're running it if you didn't have to edit grub? Does `uname -r` agree with the new version you just installed? make install symlinks the new kernel to vmlinuz and the previous one to vmlinuz.old. If grub.conf uses these names, you never need to edit it when installing a new kernel. -- Neil Bothwick Like Entropy, bugs can only be created, not destroyed. signature.asc Description: PGP signature
Re: [gentoo-user] Re: Now Know Why Portage Is So Slow
Arnau Bria wrote: On Fri, 26 May 2006 08:28:49 +0100 Neil Bothwick [EMAIL PROTECTED] wrote: make install symlinks the new kernel to vmlinuz and the previous one to vmlinuz.old. If grub.conf uses these names, you never need to edit it when installing a new kernel. Does it control if my /boot partition is mounted? make install doesn't mount /boot. Alexander Skwar -- God isn't dead, he just couldn't find a parking place. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: Now Know Why Portage Is So Slow
On Friday 26 May 2006 07:48, Alexander Skwar wrote: Hemmann, Volker Armin wrote: On Friday 26 May 2006 04:12, Lord Sauron wrote: sorry for my sin. I didn't know about eix. On 5/25/06, Bo Ørsted Andresen [EMAIL PROTECTED] wrote: Friday 26 May 2006 01:00 skrev Lord Sauron: If it's not, then I really need to ask why on earth portage takes so long to just index and search packages that took apt-get much less time to work with. I don't think it should be this slow. I'm not even talking about compile-times - I know and expect those to be slow, but just raw package searching and stuff is not that fast. Do like the rest of us. emerge eix and use that for searching. Make sure to run update-eix everytime you have sync'ed portage or better yet, use eix-sync to sync portage. -- or better, install esearch. It is as fast as eix, and it comes with esync. So instead of emerge sync AND update-eix, you just run esync. Sory, I fail to see the advantage. eix comes with eix-sync, which will do a emerge --sync and update-eix. ok, but still less to type ;) -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: Now Know Why Portage Is So Slow
Friday 26 May 2006 17:51 skrev Hemmann, Volker Armin: ok, but still less to type ;) But esearch is more than twice as long as eix... ;) -- Bo Andresen pgpsWVltWa7BV.pgp Description: PGP signature
Re: [gentoo-user] Re: Now Know Why Portage Is So Slow
On Friday 26 May 2006 18:13, Bo Ørsted Andresen wrote: Friday 26 May 2006 17:51 skrev Hemmann, Volker Armin: ok, but still less to type ;) But esearch is more than twice as long as eix... ;) I am using search less, than syncing, so still a win, and it is only eseatab ;) -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: Now Know Why Portage Is So Slow
Hemmann, Volker Armin wrote: On Friday 26 May 2006 18:13, Bo Ørsted Andresen wrote: Friday 26 May 2006 17:51 skrev Hemmann, Volker Armin: ok, but still less to type ;) But esearch is more than twice as long as eix... ;) I am using search less, than syncing, so still a win, and it is only eseatab ;) Which is still 5 characters compared to 3 characters for eix :) Alexander Skwar -- Bizoos, n.: The millions of tiny individual bumps that make up a basketball. -- Rich Hall, Sniglets -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: Now Know Why Portage Is So Slow
On Friday 26 May 2006 21:28, Alexander Skwar wrote: Hemmann, Volker Armin wrote: On Friday 26 May 2006 18:13, Bo Ørsted Andresen wrote: Friday 26 May 2006 17:51 skrev Hemmann, Volker Armin: ok, but still less to type ;) But esearch is more than twice as long as eix... ;) I am using search less, than syncing, so still a win, and it is only eseatab ;) Which is still 5 characters compared to 3 characters for eix :) but eix-sync is still longer than esync (8 to 5) ;) -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: Now Know Why Portage Is So Slow
On Sat, 27 May 2006 00:25:53 +0200, Hemmann, Volker Armin wrote: but eix-sync is still longer than esync (8 to 5) ;) alias es=eix-sync cuts it down to two, for anyone sad enough to care... or you could run it from cron. BTW how many characters have you typed in your emails to make the point that one program's name saves you 0.8s per day in typing time? ;-) -- Neil Bothwick 2 + 2 = 5 for extremely large values of 2. signature.asc Description: PGP signature
Re: [gentoo-user] Re: Now Know Why Portage Is So Slow
On Saturday 27 May 2006 00:43, Neil Bothwick wrote: On Sat, 27 May 2006 00:25:53 +0200, Hemmann, Volker Armin wrote: but eix-sync is still longer than esync (8 to 5) ;) alias es=eix-sync cuts it down to two, for anyone sad enough to care... or you could run it from cron. BTW how many characters have you typed in your emails to make the point that one program's name saves you 0.8s per day in typing time? ;-) a day? luckily I don't sync every day ... -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: Now Know Why Portage Is So Slow
On 5/25/06, Thomas Kirchner [EMAIL PROTECTED] wrote: * On May 25 11:45, Lord Sauron (gentoo-user@lists.gentoo.org) wrote: I've found (after much exploration) that there is a archive: /portage-20060123.tar.bz2 This is just a remnant from when you installed Gentoo. You can delete that file. Portage is already using uncompressed files under /usr/portage - that tarball is just a starter tarball that portage bootstraps itself with during the initial Gentoo installation. That's curious. So I can delete this tarball then? I also think that there's another file, /metadata.tar.bz2, which I think is portage-related. If possible I'd like to uncompress that as well. I've never seen a metadata tarball. metadata.xml is something portage keeps uncompressed in /usr/portage for every package. I've got one on my hard drive. You can have it if you want ; ) It takes about as long to start going as it does to open the archive /portage-20060123.tar.bz2 - conincidence? I think not! I think so ;) If it's not, then I really need to ask why on earth portage takes so long to just index and search packages that took apt-get much less time to work with. I don't think it should be this slow. I'm not even talking about compile-times - I know and expect those to be slow, but just raw package searching and stuff is not that fast. -- == GCv3.12 == GCS d-(++) s+: a? C++ UL+ P+ L++ E--- W+(+++) N++ o? K? w--- O? M+ V? PS- PE+ Y-(--) PGP- t+++ 5? X R tv-- b+ DI+++ D+ G e* h- !r !y = END GCv3.12 -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: Now Know Why Portage Is So Slow
Friday 26 May 2006 01:00 skrev Lord Sauron: If it's not, then I really need to ask why on earth portage takes so long to just index and search packages that took apt-get much less time to work with. I don't think it should be this slow. I'm not even talking about compile-times - I know and expect those to be slow, but just raw package searching and stuff is not that fast. Do like the rest of us. emerge eix and use that for searching. Make sure to run update-eix everytime you have sync'ed portage or better yet, use eix-sync to sync portage. -- Bo Andresen pgpbyR4DvNl4N.pgp Description: PGP signature
Re: [gentoo-user] Re: Now Know Why Portage Is So Slow
Lord Sauron wrote: I've got one on my hard drive. You can have it if you want ; ) I have them in /usr/portage/*/*/metadata.xml but none anywhere else though. There are none that end in .tar.bz2 though. Where is yours and where is mine? O_O Dale :-) -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: Now Know Why Portage Is So Slow
On Thu, 2006-05-25 at 16:00 -0700, Lord Sauron wrote: On 5/25/06, Thomas Kirchner [EMAIL PROTECTED] wrote: It takes about as long to start going as it does to open the archive /portage-20060123.tar.bz2 - conincidence? I think not! I think so ;) If it's not, then I really need to ask why on earth portage takes so long to just index and search packages that took apt-get much less time to work with. In defence of portage, I estimate there are 11229 packages that portage has to search through descriptions, dependencies, masks, etc: $ cd /usr/portage; find . -maxdepth 2 -mindepth 1 -type d | wc -l 11229 does apt-get really search this many packages? I don't think it should be this slow. And I don't think I should have this little money :) But seriously, I think you trade off speed when searching, vs speed when syncing, vs keeping a database up to date. As already mentioned, there are other tools to help speed it up. Also, On Thu, 2006-05-25 at 11:45 -0700, Lord Sauron wrote: I also get the bonehead award: there was a new kernel sitting on my hard drive and just yesterday I found and installed it. It was remarkably easy to install! I loaded the configuration file from my old kernel and then just make make install and it worked! I didn't even have to edit /boot/grub/menu.lst! Are you sure you're running it if you didn't have to edit grub? Does `uname -r` agree with the new version you just installed? cya, -- Iain Buchanan iaindb at netspace dot net dot au A jury consists of twelve persons chosen to decide who has the better lawyer. -- Robert Frost -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: Now Know Why Portage Is So Slow
sorry for my sin. I didn't know about eix. On 5/25/06, Bo Ørsted Andresen [EMAIL PROTECTED] wrote: Friday 26 May 2006 01:00 skrev Lord Sauron: If it's not, then I really need to ask why on earth portage takes so long to just index and search packages that took apt-get much less time to work with. I don't think it should be this slow. I'm not even talking about compile-times - I know and expect those to be slow, but just raw package searching and stuff is not that fast. Do like the rest of us. emerge eix and use that for searching. Make sure to run update-eix everytime you have sync'ed portage or better yet, use eix-sync to sync portage. -- Bo Andresen -- == GCv3.12 == GCS d-(++) s+: a? C++ UL+ P+ L++ E--- W+(+++) N++ o? K? w--- O? M+ V? PS- PE+ Y-(--) PGP- t+++ 5? X R tv-- b+ DI+++ D+ G e* h- !r !y = END GCv3.12 -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: Now Know Why Portage Is So Slow
On Friday 26 May 2006 04:12, Lord Sauron wrote: sorry for my sin. I didn't know about eix. On 5/25/06, Bo Ørsted Andresen [EMAIL PROTECTED] wrote: Friday 26 May 2006 01:00 skrev Lord Sauron: If it's not, then I really need to ask why on earth portage takes so long to just index and search packages that took apt-get much less time to work with. I don't think it should be this slow. I'm not even talking about compile-times - I know and expect those to be slow, but just raw package searching and stuff is not that fast. Do like the rest of us. emerge eix and use that for searching. Make sure to run update-eix everytime you have sync'ed portage or better yet, use eix-sync to sync portage. -- or better, install esearch. It is as fast as eix, and it comes with esync. So instead of emerge sync AND update-eix, you just run esync. Has the additional advantage, that it lists all new and updates packages, when the sync is finished. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: Now Know Why Portage Is So Slow
Lord Sauron wrote: On 5/25/06, Thomas Kirchner [EMAIL PROTECTED] wrote: * On May 25 11:45, Lord Sauron (gentoo-user@lists.gentoo.org) wrote: I've found (after much exploration) that there is a archive: /portage-20060123.tar.bz2 Much exploration? Forgive my amazement and please don't be *too* terribly offended by the rudeness of what I'm about to type, but... you call `ls /` 'much exploration'?? That's curious. So I can delete this tarball then? Yes. In fact, someone should tell the Installer people that it should clean up after itself. It takes about as long to start going as it does to open the archive /portage-20060123.tar.bz2 - conincidence? I think not! I think so ;) If it's not, then I really need to ask why on earth portage takes so long to just index and search packages that took apt-get much less time to work with. I don't think it should be this slow. I'm not even talking about compile-times - I know and expect those to be slow, but just raw package searching and stuff is not that fast. The time is how long it takes for python to 'import portage'. Unfortunately that's a limitation of the portage code - that even minor metadata searches and such can't take place without a full 'import portage'. The import is a cached process, so the metadata only has to be loaded from disk once, and is quickly used from RAM each time thereafter. If speed when searching packages is an issue, try app-portage/eix or http://gentoo-portage.com. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: Now Know Why Portage Is So Slow
Hemmann, Volker Armin wrote: So instead of emerge sync AND update-eix, you just run esync. eix-sync It's only three more keys... :P -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: Now Know Why Portage Is So Slow
On 5/25/06, Iain Buchanan [EMAIL PROTECTED] wrote: On Thu, 2006-05-25 at 16:00 -0700, Lord Sauron wrote: On 5/25/06, Thomas Kirchner [EMAIL PROTECTED] wrote: It takes about as long to start going as it does to open the archive /portage-20060123.tar.bz2 - conincidence? I think not! I think so ;) If it's not, then I really need to ask why on earth portage takes so long to just index and search packages that took apt-get much less time to work with. In defence of portage, I estimate there are 11229 packages that portage has to search through descriptions, dependencies, masks, etc: apt-get (as of Debian 3.1 Sarge) searches 33,333 seperate packages or so. $ cd /usr/portage; find . -maxdepth 2 -mindepth 1 -type d | wc -l 11229 does apt-get really search this many packages? It does more. I don't think it should be this slow. And I don't think I should have this little money :) But seriously, I think you trade off speed when searching, vs speed when syncing, vs keeping a database up to date. As already mentioned, there are other tools to help speed it up. Yeah, well... apt-get was faster on the sync and on the search. It's not fair to compare installation times, but it was also faster on calculating the dependencies. If anything, this is a indicator that I need to try and contribute to the portage project... at least contribute as much as I'm able. Also, On Thu, 2006-05-25 at 11:45 -0700, Lord Sauron wrote: I also get the bonehead award: there was a new kernel sitting on my hard drive and just yesterday I found and installed it. It was remarkably easy to install! I loaded the configuration file from my old kernel and then just make make install and it worked! I didn't even have to edit /boot/grub/menu.lst! Are you sure you're running it if you didn't have to edit grub? Does `uname -r` agree with the new version you just installed? I went through dmesg and stuff and I'm totally positive. -- == GCv3.12 == GCS d-(++) s+: a? C++ UL+ P+ L++ E--- W+(+++) N++ o? K? w--- O? M+ V? PS- PE+ Y-(--) PGP- t+++ 5? X R tv-- b+ DI+++ D+ G e* h- !r !y = END GCv3.12 -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: Now Know Why Portage Is So Slow
On 5/25/06, Thomas Kirchner [EMAIL PROTECTED] wrote: * On May 25 16:44, Daniel da Veiga (gentoo-user@lists.gentoo.org) wrote: (correct me if I'm wrong, but you installed using the Gentoo Installer, didn't you? if you had a complete experience of Gentoo install, you would know that by now, that's why I strongly advice new users to AVOID THE INSTALLER) Good point, Daniel. I totally forgot about the installer because I've never even looked at it, but you're right - the only way someone could miss that is if they used the installer or if someone else installed Gentoo for them. That said, I must reiterate the sentiment - avoid the installer like the plague. (Sorry, installer project folks. I just don't agree with it.) To the original poster, and to anyone else who has used the installer, please do the list and yourselves a favor - read the guides, learn your system. I don't mean this to be rude in any way, but you'll get much more benefit out of Gentoo that way. I'm learning Gentoo as fast and as much as I can! I've fixed many problems by myself that you haven't heard about because I managed to fix them myself. I'm not as idiotic as some, but I'm not at all familiar with portage and that's why I'm asking: I'm a hardened apt-get veteran, but with portage I'm still learning, which is why I ask. -- == GCv3.12 == GCS d-(++) s+: a? C++ UL+ P+ L++ E--- W+(+++) N++ o? K? w--- O? M+ V? PS- PE+ Y-(--) PGP- t+++ 5? X R tv-- b+ DI+++ D+ G e* h- !r !y = END GCv3.12 -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: Now Know Why Portage Is So Slow
Hemmann, Volker Armin wrote: On Friday 26 May 2006 04:12, Lord Sauron wrote: sorry for my sin. I didn't know about eix. On 5/25/06, Bo Ørsted Andresen [EMAIL PROTECTED] wrote: Friday 26 May 2006 01:00 skrev Lord Sauron: If it's not, then I really need to ask why on earth portage takes so long to just index and search packages that took apt-get much less time to work with. I don't think it should be this slow. I'm not even talking about compile-times - I know and expect those to be slow, but just raw package searching and stuff is not that fast. Do like the rest of us. emerge eix and use that for searching. Make sure to run update-eix everytime you have sync'ed portage or better yet, use eix-sync to sync portage. -- or better, install esearch. It is as fast as eix, and it comes with esync. So instead of emerge sync AND update-eix, you just run esync. Sory, I fail to see the advantage. eix comes with eix-sync, which will do a emerge --sync and update-eix. Has the additional advantage, that it lists all new and updates packages, when the sync is finished. You don't know eix, do you? Because, what you list here as an advantage is no advantage, as eix does the same. Alexander Skwar -- economist, n: Someone who's good with figures, but doesn't have enough personality to become an accountant. do -- gentoo-user@gentoo.org mailing list
