I am running openSUSE 12.3 64-bit on 6GB RAM notebook computer. I have a lowly DELL Inspiron 14R with Pentium-M but OK for my work and watching movies.
Previously I was running Fedora 18 on this lappy and after reformatted to openSUSE 12.3 and upgraded to GNOME 3.8, I find that copying files to my file server via SSH is unbearably slow i.e. 1.5GB takes me an hour. I use wireless exclusively.
On the same notebook I booted into a live Fedora 18 and tried copying a 238MB file and it took me less than 5 minutes vs more than 15 minutes required on my installed openSUSE 12.3.
The nature of my work requires me to periodically to copy large amount of files to my primary file server. I have not being able to test wired Ethernet as my cubicle has no wired connection.
This slow down is truly upsetting as it is hampering my work schedule.
Any idea on what would be the cause of this? I am quite happy with openSUSE and it would be a shame that I would need to switch back to Fedora or Ubuntu just to get some work done.
On 2013-06-13 11:16, yeoheric wrote:
>
> Hi,
>
> I am running openSUSE 12.3 64-bit on 6GB RAM notebook computer. I have
> a lowly DELL Inspiron 14R with Pentium-M but OK for my work and watching
> movies.
>
> Previously I was running Fedora 18 on this lappy and after reformatted
> to openSUSE 12.3 and upgraded to GNOME 3.8, I find that copying files to
> my file server via SSH is unbearably slow i.e. 1.5GB takes me an hour. I
> use wireless exclusively.
You could try another sending protocol to find out if it is ssh or
something different at fault. Ftp, http…
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
Copying via unencrypted protocol is not permissible, therefore using something like FTP is out of the question. I can try Samba but then Samba AFAIK cant do encrypted file transfers.
Also there is the question of trying transfer files when I am out of the office. VPN facility is not made available.
I heard that changing the I/O disk elevator to “Deadline” could solve this problem when copying/moving large files (which seem to be your case, independently from SSH). See this openSUSE documentation chapter for more details:
Unencrypted transfers can be done easily enough as long as nothing
sensitive is within the files, right? Testing throughput is trivial as
long as you control the boxes. If you have an FTP server (guessing you
don’t, based on the company rule about unencrypted stuff) then just create
a test 1 GB file with nothing in it and transfer that:
#On the “client” (sending, as in your workstation for the first test #system:
time dd if=/dev/zero bs=1024000 count=0 seek=1024 | netcat server.ip 1234
The nice thing about ‘dd’ is that it tells you throughput, just in case
you forget a timer (‘time’ on the front). As long as the “server” above
is not blocking port 1234 you should be able to listen with that first
netcat command and then send with the second (putting in the correct IP
for the server instead of ‘server.ip’). You can even try this on a single
system to see how quickly you can “transfer” data from your system to
itself over localhost. The nice thing is that neither of those commands
involve the disk, so no bottleneck there.
Hi ab, sorry I do not have root access to the server so I pretty much cant do much. I went to recently emptied cubicle and tried the wired (100BaseT) connection. Copying 1.7GB of files, it took approximately 4 minutes.
I am unsure whether it is a problem with the driver of my wireless Broadcom BCM4313 or something else.
yeoheric wrote:
> I am running openSUSE 12.3 64-bit on 6GB RAM notebook computer. I
> have a lowly DELL Inspiron 14R with Pentium-M but OK for my work and
> watching movies.
>
> Previously I was running Fedora 18 on this lappy and after reformatted
> to openSUSE 12.3 and upgraded to GNOME 3.8, I find that copying files
> to my file server via SSH is unbearably slow i.e. 1.5GB takes me an
> hour. I use wireless exclusively.
>
> On the same notebook I booted into a live Fedora 18 and tried copying
> a 238MB file and it took me less than 5 minutes vs more than 15
> minutes required on my installed openSUSE 12.3.
yeoheric wrote:
> Hi ab, sorry I do not have root access to the server so I pretty much
> cant do much. I went to recently emptied cubicle and tried the wired
> (100BaseT) connection. Copying 1.7GB of files, it took approximately 4
> minutes.
>
> I am unsure whether it is a problem with the driver of my wireless
> Broadcom BCM4313 or something else.
You have my sympathy about the no-unencrypted-transfers and the
unhelpful boss. We have a similar situation where I work in some regards.
OK, so I think we have established:
(1) It all works running Fedora 18 and wireless network
(2) It all works using openSUSE 12.3 and a wired connection
(3) It doesn’t work well using openSUSE 12.3 and wireless network
I think that makes it pretty clear that the problem is related to your
wireless connection on openSUSE.
I know next to nothing about wireless, but there is a specific wireless
forum. I suggest you read the stickies at the beginning of that forum
and then post a question there asking for help.
I also note that the title of this thread mentions Nautilus. Before
doing anything else, I suggest you try using the ssh command-line
program to make sure that the problem actually has nothing to do with
Nautilus.
Agreed… if it goes fast when wired then it’s not SSH, or nautilus, or
anything else like that.
By the way, the netcat commands presented do not require any special
privileges. As long as the system’s firewall is not blocking you should
be able to do those. The nice thing about testing from one machine to
itself is that you can verify it works syntactically and permissions-wise
(other than the firewall which you cannot change on your own) easily since
most boxes do not block localhost transfers.
Thank you all. My boss is actually a nice guy, but that being a primary file server - only the CTO would have root rights to it. It’s OK by me, since it absolves me of any responsibility should it goes up in smoke.
By the way I usually use Nautilus to copy files over SMB, NFS, SSH - coz I am just a little lazy to drop to CLI. My company does a lot of solutions based on RHEL and so we are encouraged to use Fedora/CentOS on our desktops and lappies.
In the absence of a always available wired connection - I could not realistically do a proper test.
I have done an SSH/SCP and smb access from CLI - same issue.
Guess it is a driver issue then. I used to run SLED 11SP2 on this lappy but I let the sub lapsed after I joined my present company.
Thanks to all again. Have a wonderful weekend ahead…
