FileZilla Forums

Hi,
just purchased the Pro version of FileZilla. I'm a long time user of Fugu, and already miss it tbh.

Connected to an Ubuntu 20 server (same LAN) with sftp/ssh and tried to copy the data directory of a nextcloud server to a local directory.

root@server:/.../data# du -ch .
11G total
root@server:/.../data# find . -type f | wc -l
182958

Started the transfer and FileZilla immediately locked up (spinning wheel). It "came back" about every minute to show some random progress and used 100% CPU on one core almost all the time. The local folder filled up, although quite slowly. NIC was far from saturated, and I see 3 fzstfp processes running.

[rant]This is even worse than the free 10 years old Fugu client. After about 45 minutes FileZilla finally came back to life and started to show real-time progress and was responsive to interaction. I mean, do I expect to much if I'd like to see an app in 2022 still responsive when it is doing its main purpose?[/rant]

Good thing: It finished its job after 2h without errors.

Unusual. How old is your Mac? What version of macOS are you using?

This machine is a Mac Pro, Mojave, 32GB of RAM, 6 Core Xeon@3,3GHz. The target/server is an Ubuntu 20.04 LTS VM running in a Proxmox cluster on the same LAN.

Edit: Just started copying back the data to a different server. Began fine, but after a few files same behavior: 100% CPU and the GUI is totally unresponsive. Target is an Ubuntu 22.04 server via scp/sftp on the same LAN again. The VM runs off a SSD, the local store is SSD, so I don't blame drives or I/O. Other apps on the Mac are not affected (like the browser I just use), overall CPU load is about 10% on the Mac and ~6% on the cluster.

Addendum:
After about 1 hour FileZilla does no longer provoke the beachball but is still more or less unresponsive, although it kinda shows the progress. Still >100% CPU, about 1 gig of physical RAM, 13 threads. Can move the window, switching tabs takes >10s. Does FileZilla only use a single core for everything?

All of the user interface sits in the same thread. Compared to other platforms, basic GUI stuff is slow on macOS. It helps to turn off display of the message log and queue.