You are not logged in.
Pages: 1
Bravo, bravo, BRAVO!
Pacman 3.0 is absolutely, positively blazingly FAST!
Thank you developers for making one of the best package managers into THE best package manager!
Offline
may i ask what filesystem you re using for /var ?
edit: im asking cause i had been using reiser for 8 months and recently converted to ext3 and it seems too slow now
Last edited by dolby (2007-05-21 03:43:25)
There shouldn't be any reason to learn more editor types than emacs or vi -- mg (1)
[You learn that sarcasm does not often work well in international forums. That is why we avoid it. -- ewaller (arch linux forum moderator)
Offline
I feel pacman 3.0 is slower for me.
Offline
I've been reading about all the new found speed but I've not noticed any.
That said, pacman has always been fast for me, but I'm glad it's working faster for those that found it slow before.
oz
Offline
may i ask what filesystem you re using for /var ?
edit: im asking cause i had been using reiser for 8 months and recently converted to ext3 and it seems too slow now
Try turning directory indexing on. Also, shutting off atime (if var is a different partition) makes a difference too.
Offline
I noticed pacman 3 a little faster than before. Mostly is a difference in filesystem I believe, with xfs it was a lot slower, now with ext3 (plus directory indexing) is, for example, much faster than apt-get on a similar partition.
To get something done, a committee should consist of no more than three persons, two of them absent.
--
My Github
Offline
I haven't noticed a difference, but pacman has always been fast for me.
Offline
I am using reiser with notail, noatime. ![]()
Synchronizing especially is super fast for me now. I am using the same repos as before, even after the ranking script, but I no longer have any lag from syncing; it's like -BAM-
Last edited by Misfit138 (2007-05-23 12:52:32)
Offline
I noticed a huge speed improvement when I went to pacman3. I'm running ext3 with dir_index turned on.
Offline
I haven't noticed a difference, but pacman has always been fast for me.
same here
Offline
Yeah, it feels fast(er). No complaints. I use JFS.
Somewhere between "too small" and "too large" lies the size that is just right.
- Scott Hayes
Offline
I use JFS as filesystem too and yes, i would say the same that it feels fast(er).
The only thing what looks slower as before is a "pacman -Qo /path/foo". Could this be or should i go to the optometrist?
Offline
I noticed a huge speed improvement when I went to pacman3. I'm running ext3 with dir_index turned on.
Same here, pacman3 is indeed much faster with ext3+dir_index, than pacman2 on same fs.
(I didn't turn off atime because /var is on the same partition as /)
to live is to die
Offline
I use JFS as filesystem too and yes, i would say the same that it feels fast(er).
The only thing what looks slower as before is a "pacman -Qo /path/foo". Could this be or should i go to the optometrist?
Afaik it's slower because of this : http://www.archlinux.org/pipermail/pacm … 07374.html
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Offline
Afaik it's slower because of this : http://www.archlinux.org/pipermail/pacm … 07374.html
Thanks for the nice information and that there is hope that it will get fixed.
Offline
I've noticed a _huge_ speed increase with pacman 3. I run a fairly vanilla install with ext3 defaults.
Pacman v2 could take up to 30-40 seconds the first time i used it in a session, to 5-15 seconds after that.
Now, i have like 5-10 seconds response time the first time around, and _instant_ reaction after that. My verdict?
I like!
"Your beliefs can be like fences that surround you.
You must first see them or you will not even realize that you are not free, simply because you will not see beyond the fences.
They will represent the boundaries of your experience."
SETH / Jane Roberts
Offline
pacman3 seemed alot faster for me aswell, using XFS w/ noatime,nodiratime,logbufs=8
\\ archlinux on a XPS M1530 //
Offline
pacman3 seemed alot faster for me aswell, using XFS w/ noatime,nodiratime,logbufs=8
noatime,nodiratime is from my view even a good idea for every linux filesystem and i use it with jfs too.
The disadvantage of xfs is that it caches very much in the memory and in the worst case (yes, instead of i loves linux, i never would say that it don't crashes) the result been empty files. In my case this happens with ~/.kde and all time what i perhaps have won with a faster filesysten i got loose with config my whole kde a second time. Sure, this was my error because at this time i don't backup ~/.kde.-)
Offline
I don't know if it's specific to Pacman 3 or not, but last night I left an upgrade on...
...Only to discover that something had timed out and Pacman decided this was a good reason to halt the entire download process and not retry at all.
Offline
kano wrote:pacman3 seemed alot faster for me aswell, using XFS w/ noatime,nodiratime,logbufs=8
noatime,nodiratime is from my view even a good idea for every linux filesystem and i use it with jfs too.
The disadvantage of xfs is that it caches very much in the memory and in the worst case (yes, instead of i loves linux, i never would say that it don't crashes) the result been empty files. In my case this happens with ~/.kde and all time what i perhaps have won with a faster filesysten i got loose with config my whole kde a second time. Sure, this was my error because at this time i don't backup ~/.kde.-)
I guess I'm just lucky then, I've never had any crashes so bad that I couldn't shut down properly
I also run on battery backup so power loss is not an issue for me, and I keep weekly backups of my entire /home partition (which is also on XFS) ![]()
\\ archlinux on a XPS M1530 //
Offline
kano wrote:pacman3 seemed alot faster for me aswell, using XFS w/ noatime,nodiratime,logbufs=8
noatime,nodiratime is from my view even a good idea for every linux filesystem and i use it with jfs too.
The disadvantage of xfs is that it caches very much in the memory and in the worst case (yes, instead of i loves linux, i never would say that it don't crashes) the result been empty files. In my case this happens with ~/.kde and all time what i perhaps have won with a faster filesysten i got loose with config my whole kde a second time. Sure, this was my error because at this time i don't backup ~/.kde.-)
Just out of curiosity, how do i add these options to my XFS partition? Do i replace the place that reads "default" in fstab to read noatime,nodiratime instead?
Offline
Just out of curiosity, how do i add these options to my XFS partition? Do i replace the place that reads "default" in fstab to read noatime,nodiratime instead?
Yup.
http://www.everything2.com/index.pl?node_id=1479435 is a good read if you're looking to get the most performance out of XFS.
Last edited by kano (2007-05-29 19:10:51)
\\ archlinux on a XPS M1530 //
Offline
Pages: 1