[pacman-dev] slower ftp access with pacman 3 ?
2007/5/8, Aaron Griffin <aaronmgriffin@gmail.com>:
That one is problematic and is due to the symlinking on the servers. There's no way to know what it should do because 'PWD' returns the wrong directory.
yes, I was just wondering if it was possible to detect symlinks, but I don't think ftp allows this.
Ideally we need to fix the ftp setup on the main servers and the mirrors though (0.8 should be a symlink to current, not the other way around). But you could try using the 0.8 path in your mirror config and see if that helps.
I don't know, I find it more logical to have current pointing to the current version. Having it the other way around would indeed solve the problem, but I find it a bit odd. Using 0.8 in the config directly indeed works, since it's a real directory. Anyway, this problem only occurs when downloading several packages from current. For syncing, it has to change path for each repo (current, then extra, then ...), so there is another problem. Did the ftp code change a lot between pacman 2 and pacman 3? Also, why is ftp used by default for all mirrors, even though many are available through both protocols. What's wrong with http? It has much faster access, but maybe also some obvious downsides I don't know about?
Tuesday 08 of May 2007 20:00:26 Xavier napisał(a):
2007/5/8, Aaron Griffin <aaronmgriffin@gmail.com>:
That one is problematic and is due to the symlinking on the servers. There's no way to know what it should do because 'PWD' returns the wrong directory.
yes, I was just wondering if it was possible to detect symlinks, but I don't think ftp allows this.
Ideally we need to fix the ftp setup on the main servers and the mirrors though (0.8 should be a symlink to current, not the other way around). But you could try using the 0.8 path in your mirror config and see if that helps.
I don't know, I find it more logical to have current pointing to the current version. Having it the other way around would indeed solve the problem, but I find it a bit odd. Using 0.8 in the config directly indeed works, since it's a real directory.
Anyway, this problem only occurs when downloading several packages from current. For syncing, it has to change path for each repo (current, then extra, then ...), so there is another problem. Did the ftp code change a lot between pacman 2 and pacman 3?
Also, why is ftp used by default for all mirrors, even though many are available through both protocols. What's wrong with http? It has much faster access, but maybe also some obvious downsides I don't know about?
_______________________________________________ pacman-dev mailing list pacman-dev@archlinux.org http://archlinux.org/mailman/listinfo/pacman-dev
There isn't any, as far as I know really. One could probably argue how http was overhead or didn't incorporate the similar solutions ftp could give off for anonymous file access, but frankly, those days are slightly over and ftp remains the incredibly broken by design protocol. That's what I heard at least - really, can't say that I mind either. I guess tho the recommended way would be using ftp, if not for anything else, than for proper (? quotation needed) QoS markings on firewalls/routers. Btw, I really can't say I find pacman3 slow... well, the tests do speak the truth and ofcourse if anywhere there could be an improvement made, I say go for it with my blessings - just a 'feel' however that it's pretty fast as is ;) Regards, //m. -- Mateusz Jędrasik <m.jedrasik@gmail.com> tel. +48(51)69-444-90, +44(772)664-2342 http://imachine.szklo.eu.org
On 5/8/07, Xavier <shiningxc@gmail.com> wrote:
2007/5/8, Aaron Griffin <aaronmgriffin@gmail.com>:
That one is problematic and is due to the symlinking on the servers. There's no way to know what it should do because 'PWD' returns the wrong directory.
yes, I was just wondering if it was possible to detect symlinks, but I don't think ftp allows this.
Ideally we need to fix the ftp setup on the main servers and the mirrors though (0.8 should be a symlink to current, not the other way around). But you could try using the 0.8 path in your mirror config and see if that helps.
I don't know, I find it more logical to have current pointing to the current version. Having it the other way around would indeed solve the problem, but I find it a bit odd. Using 0.8 in the config directly indeed works, since it's a real directory.
Anyway, this problem only occurs when downloading several packages from current. For syncing, it has to change path for each repo (current, then extra, then ...), so there is another problem. Did the ftp code change a lot between pacman 2 and pacman 3?
Yes, pacman moved from libftp to libdownload, a port of the BSD libfetch to Linux.
Also, why is ftp used by default for all mirrors, even though many are available through both protocols. What's wrong with http? It has much faster access, but maybe also some obvious downsides I don't know about?
Change the mirror file if you want. We aren't going to list duplicates of every server in the file, it is quite long as is. I for one find FTP to be a faster protocol over a good connection- this is usually due to server setup because their ftp daemon is set up to serve small numbers of large files, while http is set up to serve large numbers of small files. Maybe that is all placebo effect, but I seem to notice it. -Dan
I for one find FTP to be a faster protocol over a good connection- this is usually due to server setup because their ftp daemon is set up to serve small numbers of large files, while http is set up to serve large numbers of small files. Maybe that is all placebo effect, but I seem to notice it.
http://cactuswax.net/blog/just-say-no-to-ftp/ ftp is generally a faster protocol, due to the fact that for each ftp data request, there is less overhead (no http headers, etc). ftp itself is a horrible protocol though. Very poorly behaved (a pain to allow through edge network filters, harder to proxy, etc) when compared to http. there really isn't much reason to use ftp these days. I believe that the only reason it is still used, has to do with applications that you can use with ftp... Such as: - The implementation of upload 'tokens' that are often used in the gaming and underground filesharing scene - The granularity of permissions available (directory/user level). just my opinion, but I am a biased network monkey.
2007/5/8, Dan McGee <dpmcgee@gmail.com>:
Yes, pacman moved from libftp to libdownload, a port of the BSD libfetch to Linux.
thanks for clearing this up, I was a bit confused with these 3 libs.
Change the mirror file if you want. We aren't going to list duplicates of every server in the file, it is quite long as is.
I wasn't thinking about having both, just choosing the best default.
I for one find FTP to be a faster protocol over a good connection- this is usually due to server setup because their ftp daemon is set up to serve small numbers of large files, while http is set up to serve large numbers of small files. Maybe that is all placebo effect, but I seem to notice it.
ok, if http is generally only faster for syncing, and ftp is generally faster for downloading large files, then fair enough. I'll just start using http for a while, and then decide only for myself which one is better :)
participants (4)
-
Dan McGee
-
eliott＠cactuswax.net
-
Mateusz Jedrasik
-
Xavier